ROX-27129: remove tenant-resources helm chart

[ludydoo]

Description

Removing the tenant-resources helm chart.

This removes the logic branch where the reconciler could deploy the embedded tenant-resources helm chart, and assumes that ArgoCD is always enabled for tenants.

Also, the Network Policy Tests were coupled to the old tenant-resources helm chart, and had to be deleted along with the chart.

Checklist (Definition of Done)

• Unit and integration tests added
• Added test description under Test manual
• Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
• CI and all relevant tests are passing
• Add the ticket number to the PR title if available, i.e. ROX-12345: ...
• Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.
• Add secret to app-interface Vault or Secrets Manager if necessary
• RDS changes were e2e tested manually
• Check AWS limits are reasonable for changes provisioning new resources
• (If applicable) Changes to the dp-terraform Helm values have been reflected in the addon on integration environment

Test manual

TODO: Add manual testing efforts

# To run tests locally run:
make db/teardown db/setup db/migrate
make ocm/setup
make verify lint binary test test/integration

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[openshift-ci]

@hector-vido: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e

/test images

Use /test all to run all jobs.

In response to this:

/retest images

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hector-vido]

/test images

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[hector-vido]

/test images

[ludydoo]

/retest

[ludydoo]

/retest

[kovayur]

🚀

[kovayur]

Don't we still need those tests? Are we going to move them to the gitops repository? How about creating a follow-up ticket?

[ludydoo]

I'm not sure if we still need them, but I can create a follow-up ticket.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kovayur, ludydoo

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kovayur,ludydoo]

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