Update Pricing FAQ functionality to use details elements for all questions, add deep linking

Why is this change being made?

Related to https://gitlab.com/gitlab-com/marketing/inbound-marketing/marketing-website/-/issues/176

The goal is to make it easier for users to see all the FAQ questions without clicking anything so potential customers can more easily find the questions they're looking for.

This MR:

1. Expands all the FAQ questions to their own details elements on the page, with a summary element to list the question part of it.
2. Adds a show/hide all button to each category to toggle groups open/closed
3. Adds anchors to each answer that point to their corresponding question, for quick reference. @jhalloran - we initially talked about adding this on hover, which I can do, but I think it might be clearer to users to have it visible by default, which we were planning on doing on mobile anyway. What do you think?
4. Adds JavaScript to open specific details elements if their corresponding ID exists in the URL hash (i.e. /pricing#how-much-space-can-i-have-for-my-repo-on-gitlab-saas). So we can deep link to the item, scroll to it, and open it for quick reference.
5. Preserves the leap.js functionality
6. Preserves the Google Analytics "data-inbound-analytics" => "pricing-leap-target" metadata from !87650 (merged)

QA

1. Visit the review app pricing page
2. Confirm it matches the Figma file
3. Confirm appropriate functionality (show/hide all toggles, deep linking via anchor links, etc.)
4. Let me know if you want me to make the anchor icons hover-dependent on desktop. It's a quick change, I just thought this might be clearer for users.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this change to the correct DRI(s)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---