Forms sidebar doesn't open with error links from Inline Form Errors module

Problem/Motivation

Inline Form Errors replaces the error messages in the summary block at the top of the page with links to the invalid fields.

For errors inside details and vertical tabs, clicking the error link opens the details / vertical tab and focuses the invalid field.

For errors in Default Admin's closed sidebar, clicking the error link does nothing. The sidebar remains closed, and the invalid field remains hidden.

I think this causes failure of WCAG SC 3.3.3 Error Suggestion (Level AA).

Inline Form Errors moves the descriptive error messages with suggestions to the invalid fields. If users can't find the invalid fields, they also won't find the detailed error messages.

Related:

The closed sidebar provides no indication that it contains invalid fields. Working on that in #3619387: Indicate on forms sidebar toggle button that sidebar has child element errors.

Steps to reproduce

1. Set Default Admin as the admin theme.
2. Install the article test recipe (drush recipe core/tests/fixtures/recipes/article_content_type),
   or create an Article content type & install the Path module (aka path_alias).
3. Enable the Inline Form Errors module.
4. Go to /node/add/article.
5. Reduce viewport width until the sidebar on the right containing the "advanced" fields collapses.
6. Click the toggle button to expand the sidebar.
7. Enter a value without a beginning slash in the URL alias field.
8. Close the sidebar.
9. Click the Save button.
   This should cause a validation error at the top of the page, something like the following with "URL alias" being a link:
   "1 error has been found:
   URL alias".
10. Click the "URL alias" link in the error message.

Expected

1. The sidebar is opened.
2. Focus moves to the invalid URL alias field.

Actual

Nothing happens when the "URL alias" link is clicked.

Proposed resolution

Listen for formFragmentLinkClickOrHashChange events and open the sidebar, as with details elements.

Remaining tasks

1. Create merge request.
2. Review.
3. Make the decision regarding jQuery (frontend framework manager or higher?).

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet