Create reusable Observability Provisioning UI

What does this MR do and why?

• Rename Observability Client Provisioning API to be more generic (enableTraces -> enableObservability )
  • Deprecated old ones for temporary backward compatibility. Removed in 2nd part !134748 (merged)
• Add generic and reusable ObsevabilityEmptyState component, that can be reused for all Observability features
• Add reusable ProvisionedObservabilityContainer
  • This handles the provisioning logic and UI, so that each component that is wrapped in the ProvisionedObservabilityContainer does not need to handle the provisioning logic and UI itself. This is useful as we are introducing a new Observability Metrics feature and we will need to show the same Provisioning UI used for Tracing.

Prerequisite for metrics: Add Provisioning UI (gitlab-org/opstrace/opstrace#2437 - closed)

There is a second MR where these new components are used: !134748 (merged)

Screenshots or screen recordings

How to set up and validate locally

NA as new components are not hooked up yet

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.