Expand pre-checks of user file source & object store configs

[jmchilton]

A really expansive version of what I had in mind for the first big section in https://github.com/galaxyproject/galaxy/issues/18128.

• UI (checklist) for detailed display of errors - in follow up PRs I'll add "writability" check to the checklist but one can imagine a lot of room for growing this (screenshot 3)
• UI option to test configuration from management menu. (screenshot 4)
• API + UI for checking configuration before upgrading to new version of template (with unit tests).
• API + UI for checking configuration before updating current template's settings (with unit tests).
• Add an option during update/upgrade to allow forcing the update even if configuration doesn't validate - I don't allow creation of invalid things, but if there are problems with an existing thing - admins and power users should have recourse. It is their data. (screenshot 2)
• General unit test expansion for the backend and refactoring the frontend toward composables to reduce the duplication between the object store and file source versions of the various forms.

---

A simple file source pointing at a public S3 bucket - inside edit setting form (pre-existing functionality)

---

Alert (existing in 24.1 for only create but now works during update and upgrade also) with new button to expand full information in all three contexts along with the ability to force save anyway when the alert is visible:

---

Expanded Checklist for Detailed View when that button is clicked (or when menu option is clicked from index)

---

New Menu Option to Test Instance Configuration

---

How to test the changes?

• [x] I've included appropriate automated tests.

License

• [x] I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.