ROX-26065: Observability subchart teardown

[kovayur]

Description

Problem

When you uninstall the obserability helm subchart, the CR is deleted together with the operator and the namespace, which causes the CR and the namespace to remain stuck in the uninstallation state

Proposed solution

In order to shutdown the observability operator gracefully you need to perform the following sequence of actions:

1. Set observability.customResourceEnabled=false to delete the CR and effectively uninstall prometheus, alertmanager and grafana but, keep the operator and most importantly the PVCs associated with prometheus and alertmanager.
2. Set observability.enabled=false to uninstall the operator

As a result, the rhacs-observability namespace and the PVCs are NOT removed in order to retain the existing metrics.

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

[kovayur]

Required for smooth migration to argo cd. This subchart is going to be removed after the migration is completed

[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