mgr/dashboard: avoid re-enabling telemetry - #70776

Fixes: https://tracker.ceph.com/issues/78958
Signed-off-by: Anurag Raut [email protected]

PR Description:

This PR avoids re-enabling the Telemetry module when it is already enabled.

During the initial Telemetry configuration, the dashboard enables the Telemetry module and applies the selected configuration. For subsequent configuration updates, the dashboard now updates only the configuration without issuing another Telemetry enable request, preventing redundant activation attempts. The success notification is also updated to distinguish between initial activation and subsequent configuration updates, and the user is redirected after a successful operation to prevent repeated submissions.

Screencast:

Contribution Guidelines

• To sign and title your commits, please refer to Submitting Patches to Ceph.

• If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

• When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Component impact
  • Affects Dashboard, opened tracker ticket
  • Affects Orchestrator, opened tracker ticket
  • No impact that needs to be tracked
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includes unit test(s)
  • Includes integration test(s)
  • Includes bug reproducer
  • No tests