Self-service not activated for team created with initial values

[Matthias Erll]

Describe the bug:

When creating a team directly with the Otomi install (values file), ingress/egress network policy self-service is activated by default; but when attempting to create a service as a team member, the fields for Exposure and Network Policies are greyed out.

To Reproduce
Steps to reproduce the behavior:

1. Create a values file with team labs directly on Otomi install
2. Activate Otomi, then create a user labs-user in group team-labs.
3. Log in as labs-user.
4. Create any workload (e.g. a database) and deploy. Wait to finish.
5. Go to Services, and select any available service / port.
6. See that all options below are greyed out.
   (Workaround from here):
7. Log back out, log back in as an admin user.
8. On team labs, deactivate the two self-service checkboxes for Ingress and Network Policy, then Deploy
9. Once the pipeline is through, activate these self-service checkboxes again, then Deploy
10. Once the pipeline is done, log in as labs-user again and see that options from 6. can be used.

I have not observed the same behavior, if the team was only created after the Otomi install.
Also I noticed that the checkboxes in the Team view are grey, not highlighted (e.g. red) as the others.

Update:
I noticed, when explicitly adding the selfService entries to the team values file, the ingress and network policy can be modified. However, if not allowing the self service is the default, then the checkboxes should also not be set in Otomi console initially.

Expected behavior:

If the self-service on these two options is activated, I would expect the ingress and network policy self-service to be active directly on the first attempt to create a service.

Versions: 2.4.0