[FEATURE] Add disable_auto_refresh config

[mixturesolutions]

Description

Adds an optional admin config flag to centrally disable dashboard auto-refresh, addressing perses/perses#4295

Default: false (no behavior change unless explicitly enabled)

When enabled:

• The auto-refresh interval dropdown is greyed out and non-interactive
• Tooltip: “Auto-refresh has been turned off by your administrator.”
• Dashboard refreshInterval and ?refresh= URL param are ignored
• Follows the same pattern as disable_custom and disable_zoom

Note this is linked with another PR in the main perses repo

Screenshots

To enable, change in the respective perses config yaml file like the following:

Once the changes are deployed, config page will reflect the changes and the dashboard ui will look like:

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.
• E2E tests are stable and unlikely to be flaky.
  See e2e docs for more details. Common issues include:
  • Is the data inconsistent? You need to mock API requests.
  • Does the time change? You need to use consistent time values or mock time utilities.
  • Does it have loading states? You need to wait for loading to complete.

[jgbernalp]

@mixturesolutions mind checking the tests and lint failures?

[jgbernalp]

Not sure if we need all this logic to set the refresh interval to a default one. It complicates the logic when the admin re enables it as is persistent in the URL and there is no path to reset it to the default value that might come from the dashboard. If the refresh action is already gated we might not need to edit the query params.

[mixturesolutions]

Not sure if we need all this logic to set the refresh interval to a default one. It complicates the logic when the admin re enables it as is persistent in the URL and there is no path to reset it to the default value that might come from the dashboard. If the refresh action is already gated we might not need to edit the query params.

You are absolutely right, I simplified this and a lot more, only keeping the necessary changes. Everything should work now.