GUI/ENH: add template steps to passive and active checkout GUI

[tangkong]

Description

• Adds TemplateConfigurationPage and TemplateRunWidget for editing and running Template-steps in the atef config gui.
  • Plugs TemplateStep/TemplateConfiguration into the various "maps" we have littered around the repo.
• Plugs a few holes from previous PRs. (There should be no more holes, since this should be the last Template step PR)

Motivation and Context

In a bit of laziness / DRY, I've used the same pages for both the active and passive checkout cases.

There's a bit of finicky business when it comes to preparing checkouts with template-steps. As is, the step/config fails to prepare if the file is invalid. This will cause the entire page to fail. In my initial formulation this was the proper thing to do, but I'm starting to think it's not transparent enough about its failure mode.

How Has This Been Tested?

Interactively, primarily. I'll be seeing if I can't blow up the test suite by trying to build one of these widgets in CI.

Where Has This Been Documented?

This PR

Pre-merge checklist

• [x] Code works interactively
• [x] Code contains descriptive docstrings, including context and API
• [x] New/changed functions and methods are covered in the test suite where possible
• [x] Code has been checked for threading issues (no blocking tasks in GUI thread)
• [x] Test suite passes locally
• [x] Test suite passes on GitHub Actions
• [x] Ran docs/pre-release-notes.sh and created a pre-release documentation page
• [x] Pre-release docs include context, functional descriptions, and contributors as appropriate

[tangkong]

I'm going to request help QA'ing this. I'm still isolating and fixing bugs, but maybe another set of eyes will turn up some new bugs to squash

[ZLLentz]

If you still have some known bugs you're squashing, I'll give this ~15mins as a QA and review the actual code later when you've tracked them down.

[ZLLentz]

I didn't find any technical bugs for this PR in my QAing, just some user experience things. In general everything worked as intended and I could see this getting a lot of use for beamline checkouts.

UX stuff related to this PR:

• A TemplateConfiguration with no edits fails to load in run mode. You can work around this by doing an edit from one string to the same string. I think users will expect to not need to be able to do this.
• TemplateConfiguration failure reasons don't bubble up to the top-level reports. It's not possible to check why a certain template's step failed. I think users will expect the failure reasons to appear in the report (though I think it's OK if you can't click into the subtree),
• While in the GUI, a file with a TemplateConfiguration needs to be closed and re-opened entirely to pick up changes if the referenced template is updated. I think users will expect some way to manually reload template files.

Other discoveries, probably pre-existing conditions:

• If you switch a comparison's data type from e.g. float to enum and leave the combobox alone, it doesn't actually edit the dataclass in such a way to save a change. You have to manually re-select e.g. FALSE again. (Found because my test case was failing on 0.0 != 0/FALSE)

[tangkong]

I actually don't have any current bugs, but just sort of assume that some will pop up as I continue to play around with it 😢

I might address results-propagation and reports in a followup PR. I think it'll be a bit involves and probably deserves a focused look

[ZLLentz]

Maybe I should give this a full code review tomorrow then? I'm currently braining worse than expected with heat + post-race stuff.

[tangkong]

Feel free to punt until you have the time. I need to stop looking at ATEF for a bit, starting to reach a state of semantic satiation...

[tangkong]

The atef hydra strikes again 🐍