feat: Syncing of proxy settings and self-signed cert to the user's workspace namespace

[metlos]

What does this PR do?

Reference: https://issues.redhat.com/browse/CRW-2397
This adds the ability to sync settings to the workspace namespaces of the users.

The new controller watches namespaces (or projects on OpenShift). If a namespace has appropriate label (org.eclipse.che/workspace-namespace-owner-uid), it is considered a user workspace namespace and is synced to.

The value of the label is supposed to be the UID of the user. On OpenShift, this is the UID of the user object and on Kubernetes, the UID of the user as obtained from the OAuth token of the configured OIDC provider.

What issues does this PR fix or reference?

eclipse-che/che#20168

How to test this PR?

create a namespace, label it and check that the proxy settings are synced to it in a config map and self signed certificates in a secret.

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Custom resource definition file is up to date
• OLM bundles are up to date
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tolusha]

/retest

[sleshchenko]

Suggested change

	type DevworkspaceState int
	type DevWorkspaceState int

it would be a consistent naming I think, but that's not critical

[metlos]

Hmm, from looking at CO codebase, we're consistently "Devworkspace" :) So I'd like to keep it out of this PR and deal with it in another issue. But you're of course right, we should use the same terminology...

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: metlos, sleshchenko, tolusha

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[max-cx]

@tolusha, a Yes/No question about this issue:

Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide?

Yes/No?

[max-cx]

@metlos, could you please clarify what the user experience impact of this is (for the sake of writing the Release Notes text)?
You can reply here or comment in https://issues.redhat.com/browse/CRW-2397.

[tolusha]

@max-cx
No