Fix FAQGroup autofocus with Alloy issue

[stamat]

Summary

I gated the focus logic via the initialRender ref to move focus on arrow navigation. However, the Alloy actually triggers the render of the FAQGroup component, which causes the initialRender ref to be set to false. This causes the autofocus to the first FAQGroup element and the page is scrolled to it.

This PR changes the logic to gate the focus logic via the hasInteracted state instead of the initialRender ref. This way, the focus logic is only triggered after the user has interacted with the FAQGroup component.

This issue is only present in development environment probably due the Alloy dev setup...

List of notable changes:

• updated FAQGroupProps type to include hasInteracted state because the focus logic is gated via the hasInteracted state instead of the initialRender ref.

What should reviewers focus on?

This can only be tested on the dotcom pages where the FAQGroup component is used, for instace /features/copilot. Arrow navigation should move the focus correctly and the page should not scroll to the first FAQGroup element on initial render.

Supporting resources (related issues, external links, etc):

• https://github.com/github/marketing-platform-services/issues/3167#issuecomment-2191895803

Contributor checklist:

• All new and existing CI checks pass
• Tests prove that the feature works and covers both happy and unhappy paths
• Any drop in coverage, breaking changes or regressions have been documented above
• New visual snapshots have been generated / updated for any UI changes
• All developer debugging and non-functional logging has been removed
• Related issues have been referenced in the PR description

Reviewer checklist:

• Check that pull request and proposed changes adhere to our contribution guidelines and code of conduct
• Check that tests prove the feature works and covers both happy and unhappy paths
• Check that there aren't other open Pull Requests for the same update/change

[changeset-bot]

🦋 Changeset detected

Latest commit: bc3f4f6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@primer/react-brand	Patch
@primer/brand-primitives	Patch
@primer/brand-e2e	Patch
@primer/brand-fonts	Patch
@primer/brand-config	Patch
@primer/brand-storybook	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🟢 No design token changes found

[github-actions]

🟢 No visual differences found

Our visual comparison tests did not find any differences in the UI.

[rezrah]

👍

This issue is only present in development environment probably due the Alloy dev setup...

@stamat the change looks fairly context-agnostic to me, so I think it's fine. Just an FYI for future that we don't wanna put dotcom-specific fixes into Primer Brand, as the library is used outside the monolith too.