Open accordions using URL hashes

[dpfens]

This change allows users to link directly to an opened accordion.

Page section tracking via URL hash is modified to exclude headings within page accordions, as those headings would override the open accordion's hash on-page.

The logic generates the URL hash from the accordion title (“How do I set up two-factor authentication (2FA)?” becomes “how-do-i-set-up-two-factor-authentication-2fa”). But the hash/ID can be overridden using the “slug” parameter when including the accordion component.

{% capture accordionContent %}
    My test content here
{% endcapture %}

{% assign accordionContent = accordionContent | markdownify %}
{% include components/accordion.html title='How do I add an accordion with a custom ID?' slug='accordion-custom-id' content=accordionContent %}

The hash is added/removed from the URL when users open/close the accordions.

Also adds a missing js.map file.

[IanLee1521]

I admit I'm not the best front end expert, but this seems reasonable to me.

[dpfens]

@IanLee1521 @hauten I just added a change to allow users to manually specify the id/slug of the accordion, both for SEO purposes, and to avoid potential conflicts with other components on the page

[LRWeber]

Looks like it does what it set out to do! This should resolve #671

I have included some nitpicky formatting suggestions. We've (unfortunately) yet to establish standards for JS the way we have for Python, but ideally a file should at least be consistent in itself.

[dpfens]

Added Matomo tracking code for tracking accordion opens