LG-7205: Log click on in-person troubleshooting option

[aduth]

Why: To have better insight into the user's journey through in-person proofing.

Testing Instructions:

1. Navigate to http://localhost:3000
2. Sign in
3. Navigate to http://localhost:3000/verify
4. Complete proofing flow up to document capture
5. Upload attention result YAML test documents
6. Click Submit
7. Click "Verify your identity in person"
8. In your terminal, run tail -n2 log/events.log
9. Observe logged event for "IdV: verify in person troubleshooting option clicked"

[aduth]

A bit of a cheat, but working as intended: Because FormSteps reflects the step as encoded in the URL hash fragment, we can link directly to the step, rather than using the submit button (BlockSubmitButton) to navigate as a submission of the step.

This was a workaround to an issue where onClick wasn't being called due to the fact that we were only spreading props on the link version of the option, not the button version:

identity-idp/app/javascript/packages/components/troubleshooting-options.tsx

Lines 52 to 56 in 93a5f05

	<BlockLink {...extraProps} href={url}>
	{text}
	</BlockLink>
	) : (
	<BlockSubmitButton>{text}</BlockSubmitButton>

[NavaTim]

If we update these tests later, then I'd like to see this refactored to be more white-box or black-box rather than straddling the two by using getAllByRole with white-box checks. Combining the two like this reduces the assurance that the elements will behave as expected.

Probably would be good enough here to add an expect that the fetched elements are instances of HTMLAnchorElement, or to fetch using the tag name.

[aduth]

Yeah this inconsistency is necessary to appease both Testing Library and TypeScript:

• Testing Library because it intentionally doesn't provide element querying utilities to encourage testing as the users (and assistive technology) would interact with the application.
• TypeScript because it wouldn't expect #target to exist on anything other than an anchor element.

It would be nice if there were some way to test to see that the link opens in a new tab without referencing the attribute value directly like this, so we could avoid casting the result of getByRole.

[NavaTim]

LGTM