Feat: Support for Project Cloning

[CGoodwin90]

Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for changelog and subsystem label(s) applied

Various changs to support the project cloning workflow

• Adds cases for projectclone & projectclonerestore tasks in the consumer + running the clone task in tasks_handler
• Allows advanced task pods to scan for RWX volumes in the namespace & mount them in a specified location
• Sets up Tasks to be able to run as rootless

Required for uselagoon/lagoon#4072

[bbenesh]

This PR addresses uselagoon/lagoon-product#3

[bomoko]

Is there anywhere where this is actually documented? The fact that this is where things will get mounted? More a question than a request or whatever.

[CGoodwin90]

The only place I've seen it documented is in the issue on the Product board?

[bomoko]

it's pretty intense :)

[shreddedbacon]

its intense, but it is required in some form to check these variables for the feature flag to ensure the task pod gets the right fsgroup options

[CGoodwin90]

Yeah I wasn't sure if this was overkill or not, I just replicated here what we're doing in the build deploy generator to make sure we're covering all the cases. I can take a look and see if there's a nicer way to it

[shreddedbacon]

for reference, this is the original source

remote-controller/internal/controllers/v1beta2/build_helpers.go

Lines 420 to 429 in d33ac54

	lagoonProjectVariables := &[]helpers.LagoonEnvironmentVariable{}
	lagoonEnvironmentVariables := &[]helpers.LagoonEnvironmentVariable{}
	_ = json.Unmarshal(lagoonBuild.Spec.Project.Variables.Project, lagoonProjectVariables)
	_ = json.Unmarshal(lagoonBuild.Spec.Project.Variables.Environment, lagoonEnvironmentVariables)
	// check if INTERNAL_REGISTRY_SOURCE_LAGOON is defined, and if it isn't true
	// if this value is true, then we want to use what is provided by Lagoon
	// if it is false, or not set, then we use what is provided by this controller
	// this allows us to make it so a specific environment or the project entirely
	// can still use whats provided by lagoon
	if !helpers.VariableExists(lagoonProjectVariables, "INTERNAL_REGISTRY_SOURCE_LAGOON", "true") ||

[shreddedbacon]

i think its fine to leave it the way it is, unless you can figure out a better refactor that accomplishes the same result :D