Show / hide configuration associations (PP-4022)

[tdilauro]

Description

Add an expandable disclosure panel to each row on the integration/configuration list pages, showing the libraries / roles associated with that service. Users can expand/collapse individual rows or use Expand all / Collapse all controls. Alt+Click on any toggle expands or collapses all rows at once.

This is implemented as a set of overridable template methods on GenericEditableConfigList:

• getAssociatedEntries — returns entries to display (or undefined to suppress the toggle entirely)
• formatAssociatedCount — controls the count label (e.g. "3 libraries", "2 roles", "1 registered library")
• getAllLibraries — resolves short names to display names and edit links

Each component overrides as needed:

• Collections / base class — shows associated libraries
• DiscoveryServices — shows successfully registered libraries with their registration stage
• IndividualAdmins — shows admin roles; sitewide roles (manager-all, librarian-all) are pinned to the top; system admins show a synthetic "sysadmin" entry
• Libraries — suppresses the panel (libraries are not associated with other libraries)

Also includes a few minor fixes picked up along the way:

• UNSAFE_componentWillMount update to componentDidMount,
• (window as any).FormData updated to FormData,
• .catch() added to save() to suppress unhandled-rejection warnings, and
• CollectionData now explicitly declares marked_for_deletion.

Motivation and Context

Admins currently have no way to see which libraries are associated with a service without opening each service's edit form individually.

[Jira PP-4022]

How Has This Been Tested?

• Manual testing in local development environment.
• New tests for added functionality.
• CI checks pass.

Checklist:

• I have updated the documentation accordingly.
• All new and existing tests passed.

[jonathangreen]

This looks great to me @tdilauro! This is a feature that I've wanted to see for a long time. 🎉

As always, my caveat with front-end reviews is that I only know enough here to be dangerous. I added a couple of minor comments to consider, but they may or may not be relevant.

[jonathangreen]

Minor comment / question on this one: Does aria-hidden mean that keyboard users can't land on this control? Otherwise couldn't a user tab into this control, but not get the announcement for it?

[tdilauro]

Good catch. I forgot to take it out of the tab order.

[jonathangreen]

Minor: Since we add tests/jest/components/EditableConfigList.test.tsx, shouldn't these new tests go there instead?

[tdilauro]

I put these in here because I was being lazy and using the old enzyme style tests. But I'll move them over to jest/react testing library.