Per Lindsey: Keep this in NEW for now.

We need to rename the "rhsm" ClowdApp to something more specific and descriptive.

Currently, the file deploy/rhsm-clowdapp.yaml creates a ClowdApp named "rhsm" that's only used in ephemeral environments to set up testing infrastructure (like unleash feature flags and OpenTelemetry configuration). The problem is that "rhsm" is way too generic and confusing - it sounds like it represents all RHSM subscription components (like swatch-producer-azure, swatch-producer-aws, swatch-billable-usage, etc.), when in reality it's just a helper ClowdApp for testing purposes.

This confusion makes it harder to understand what's actually being deployed and can lead to mistakes when working with the codebase or configuring deployments. We should rename it to something that clearly indicates its purpose, like "rhsm-ephemeral-resources".

Acceptance Criteria

• Rename the ClowdApp in deploy/rhsm-clowdapp.yaml to a more descriptive name that clearly indicates it's for ephemeral testing infrastructure
• Update the reference in app-interface (data/services/insights/rhsm/cicd/deploy-clowder.yml line 133) to use the new name
• Update all Konflux integration tests to deploy this component "--component <NEW NAME>"
• Verify that ephemeral deployments still work correctly with the new name