Description

• Set OwnerReferences to Poolmanager and builderManager deployment and service created by environment.
• Set OwnerReferences to deployment, service and HPA created by newdeploy function.
• Set OwnerReferences to builderManager deployment and service created by environment.
• Set OwnerReferences to deployment, service and HPA created by container function.

Which issue(s) this PR fixes:

Fixes #2962

Testing

OwnerReferences are added for poolmanager deployement as follows:

$ kubectl get deploy poolmgr-go-122-default-253070 -oyaml
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
    executorInstanceId: lpd23pfg
  creationTimestamp: "2024-06-25T06:09:57Z"
  generation: 1
  labels:
    environmentName: go-122
    environmentNamespace: default
    environmentUid: e833d7f4-27bf-4f0d-9fe5-9d6169246de7
    executorType: poolmgr
    managed: "true"
  name: poolmgr-go-122-default-253070
  namespace: default
  ownerReferences:
  - apiVersion: fission.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: Environment
    name: go-122
    uid: e833d7f4-27bf-4f0d-9fe5-9d6169246de7
  resourceVersion: "253399"
  uid: c29919bf-4541-4c92-af66-696555bae54f

Tried following tests scenarios:
Test 1:
Create env.
Create poolmanager, newdeploy and container function.
Delete poolmanager, newdeploy and container function.
Result:
1. No issues, all resources were deleted.

Test 2:
Create env.
Create poolmanager, newdeploy and container function.
Delete Environment.
Result:
1. Fission-CLI failed to delete environment, env is used by atleast one function.
2. kubectl deleted the environment along with poolmanager deployment, builder deployement and builder service. Poolmanager function is not deleted but it does not work as expected.

Test 3:
Create env.
Create poolmanager, newdeploy and container function.
Update poolmanager, newdeploy and container function.
Result:
1. Successfully updated the functions.

Checklist:

• I ran tests as well as code linting locally to verify my changes.
• I have done manual verification of my changes, changes working as expected.
• I have added new tests to cover my changes.
• My changes follow contributing guidelines of Fission.
• I have signed all of my commits.