Add WLM workload group settings UI

[dzane17]

Description

Adds dashboard support for the per-workload-group settings block introduced in OpenSearch 3.7 (#20536, #21143, #21523, #21721). Administrators can now set, update, and remove the six supported keys directly from the WLM Workload Management UI on both the create and edit flows.

Documentation: opensearch-project/documentation-website#12444

What's new

A new Group settings section on the Settings tab of the WLM details page, mirrored as a panel on the create page. Each row carries the raw API key (search.max_buckets, override_request_values, etc.), a short description, a Set toggle, and a typed input.

Things to note

• Version gate. New isWlmGroupSettingsSupported(version) helper hides the section on data sources < 3.7, mirroring the existing isSecurityAttributesSupported ≥ 3.3 pattern.
• Live validation. Each input is validated as the user types — search.max_buckets ≥ 0, time values match 250ms / 30s / 1m, integers respect their per-key minimum. Invalid rows show an inline error and disable Apply Changes. Constraints live in a single table (WLM_SETTING_DEFS) — adding a new key is a one-row append.

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dzane17]

Security check failure will be resolved by #527

[KishoreKicha14]

@dzane17

1. instead of having search.default_search_timeout as label. can we have it as text
2. can we say enabled instead of set?
3. if we have dont set what value does it settings point to?

[KishoreKicha14]

can you also fix the failing cypress tests?

[dzane17]

@KishoreKicha14 Good points

1. I am not sure that is necessary. The technical name is needed to associate the WLM setting with it's corresponding cluster setting and request param. And for understanding, each setting has a one-liner below.
2. Done
3. If the WLM group setting is not defined it will fall back to whatever cluster or request value was present before this feature. I have added a small explanation under this section header.

[KishoreKicha14]

LGTM! Thanks @dzane17 for the PR..