LG-6066: Implement print button on FSMv2 Personal Key step

[aduth]

Why:

• So that we can retain feature parity with the existing screen.
• To reduce size and scope of common application bundle
• To create a more rigid connection between print JavaScript functionality and server-side render logic
• To improve test coverage for existing print button behavior

Testing Instructions:

1. Set idv_api_enabled: "true" in local config/application.yml
2. Go to: http://localhost:3000/verify/v2/personal_key
3. Click "Print"
4. Observe that print dialog is shown

[zachmargolis]

LGTM

[zachmargolis]

Is there a reason that a separate component is preferable to just a <Button onClick={print}> with maybe like a shared helper function for print that might be easier to mock?

I guess this is easier to match between client/server?

[aduth]

Is there a reason that a separate component is preferable to just a <Button onClick={print}> with maybe like a shared helper function for print that might be easier to mock?

I guess this is easier to match between client/server?

Yeah, in my mind it helps provide some extra assurances that the behavior and default label are consistent. The idea of omitting customizable label is intentional to try to enforce some consistency with how these buttons are presented.

Also, components are cheap. I think the bar should be pretty low for when it makes sense to create one.