Improve experiment/ensemble name validation in GUI

[larsevj]

Issue
Resolves #8612

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure tests pass locally (after every commit!)

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[larsevj]

Current status:

• Currently there is no actual validation done for experiment names, you can just ignore the red box and press run
• In the create experiment dialog the only requirement is that the length of the field must not be 0
• The target ensemble is not validated in ensemble experiment currently

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.96%. Comparing base (d8b17e4) to head (25b3f42).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8646      +/-   ##
==========================================
+ Coverage   90.90%   90.96%   +0.06%     
==========================================
  Files         343      343              
  Lines       21271    21288      +17     
==========================================
+ Hits        19336    19365      +29     
+ Misses       1935     1923      -12     

Flag	Coverage Δ
gui-tests	76.16% <100.00%> (+0.05%)	⬆️
integration-tests	53.35% <21.81%> (-0.07%)	⬇️
unit-tests	68.96% <21.81%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[larsevj]

There are still some remaining issues:

• Nothing stops you from setting target_ensemble in es_mda restart or manual update in such a way that you get multiple ensembles with the same name. We would then have to validate the substituted '%d', and know how many iterations are to be run.
• I believe there is still no backend validation in storage for uniqueness of names.

I think this should still work fine if you have already duplicate experiment names in storage, validation only happens when you try to create a new experiment.

[oyvindeide]

Looks good, but think there might be something with restart runs with es-mda? If I run an ensemble experiment, and then switch to the es-mda tab and manually enter: ensemble_experiment as the name, and then check the Restart run checkbox I am not able to start an experiment.

Also feel free to rebase and force push.

[larsevj]

Looks good, but think there might be something with restart runs with es-mda? If I run an ensemble experiment, and then switch to the es-mda tab and manually enter: ensemble_experiment as the name, and then check the Restart run checkbox I am not able to start an experiment.

Should be fixed now.

[oyvindeide]

LGTM! Nice work!