Some owner references should not be marked as controller.

[GrahamDumpleton]

Describe the bug

Owner reference from WorkshopSession back to WorkshopEnvironment, and from WorkshopEnvironment back to TrainingPortal, set the controller property to true. These should not really set controller to true since the owner reference only exists in this case to ensure garbage collection, and are not necessarily indicative of what is the controller in the Kubernetes sense of what is a controller.

Lots of other arbitrary resources created for environments and sessions similarly set controller to true when can be argued they shouldn't. Should review all owner references and perhaps set controller to false in most cases.

Additional information

No response