docs: add documentation for multirm

[carolinaecalderon]

Reverted

#9053

Description

Update configuration docs & add a release note for multirm.

Test Plan

N/A

Commentary (optional)

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

Ticket

RM-78

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	cfa5313
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/65fb171d7c424100089ab4c4
😎 Deploy Preview	https://deploy-preview-9016--determined-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[tara-det-ai]

added comments w suggested edits

[tara-det-ai]

see comments

[NicholasBlaskey]

Suggested change

	- WebUI: Add ability to view resource manager name for resource pools.
	- API/CLI/WebUI: Route any requests to resource pools not defined in the master configuration to
	the default resource manager, not any additional resource manager, if defined.
	- Configuration: Add a ``name`` and ``metadata`` field to resource manager section in the master
	configuration. Add an ``additional_resource_managers`` section that follows the
	``resource_manager`` and ``resource_pool`` configuration pattern.

These notes feel extraneous to me.

I think the release note should be pretty brief and just announce the feature and not get into the details.

[carolinaecalderon]

Where else would we put them? I think each of these changes are important for the end user to know -- we make release notes regularly for config changes, and changes in API behavior. We don't currently have a dedicated page to multiRM, so I thought they'd belong here

[tara-det-ai]

I also like these updates in release notes for the reasons i posted in earlier comment. release notes are a great place to keep this info. if the users don't like it, they can skip it. it helps internally with cross referencing when we go back in later and check release notes against docs during doc reviews.

[tara-det-ai]

added suggested edits and resolutions