Registry-driven Batch Events dispatch and scripts manager

[krowvin]

Parent: USACE/cwms-data-api#1772

Summary

• Adds Batch Events script registry fields for execution source, runtime, resource profile, timeout, schedule timezone, environment variables, and required roles.
• Adds registry-driven dispatch for GitHub file paths and trusted commands, shared runtime job definitions, brokered runtime env/secrets, office-scoped logs/status, and local timeout enforcement.
• Updates Scripts Manager with a stacked selector, top-pinned edit controls, repository path browsing, command mode, env-var row editing, resource profile labels, and timezone-aware schedule controls.

Validation

• python -m pytest tests\cwms_batch_events\local\test_executor.py tests\cwms_batch_events\ui\test_scripts_manager_source.py -q
• python -m pytest tests\cwms_batch_events\api\test_scripts.py tests\cwms_batch_events\ui\test_scripts_manager_source.py -q
• npm run build

Thoughts

• Do we want one big image, or should each language/runtime be it's own image?

Screenshots

Scripts Manager list

Edit form, top controls

Edit form, source/runtime/resource controls

New command script

Secret-name allow-listing

[krowvin]

Added screenshots from the local Batch Events UI after the latest Scripts Manager pass.

While capturing these I found and fixed one UI state issue: the Scripts Manager form was using Groundwork Dropdown for controlled values, but that component keeps its own initial option state. The form now uses controlled native selects for source/runtime/resource profile/schedule type, so editing SWT hourly jobs correctly shows Shell instead of falling back to the first option.

Scripts Manager list

Edit form, top controls

Edit form, source/runtime/resource controls

New command script