Add StatusPageComponent for standard status page layout

[aduth]

Why:

• To minimize developer effort in implementing status pages (error, warning, info), and to address currently inconsistencies among them.
• To address the implementation concerns at Fix countdown JavaScript error for lockout screens #6129 (comment), by (mostly) avoiding inheritance-based presenter object associated with failure screens.

Currently, this merges to #6129, since it implements the "ideal long-term solution" mentioned in #6129 (comment).

Future work would refactor to replace use of app/views/idv/shared/_error.html to use this component instead, as they serve largely the same purpose.

Testing:

1. Visit http://localhost:3000/sign_up/cancel
2. Try signing in while locked out
   • Easiest method is via rails c console: User.find_with_email('me@example.com').update!(second_factor_locked_at: Time.zone.now + 10.minutes)

Screenshots:

(Note: There are not expected to be any visual differences with these changes)

Screen	Screenshot
Sign Up Cancel
MFA Lockout

[aduth]

Future work should adapt app/views/shared/_troubleshooting_options.html.erb into a component, so this could be implemented as a pass-through similar to PageHeadingComponent and ButtonComponent above.

Suggested change

	renders_one :troubleshooting_options
	renders_one :troubleshooting_options, ::TroubleshootingOptionsComponent

[zachmargolis]

LGTM!

[zachmargolis]

yesss down with inheritance!

[zachmargolis]

should we consider refactoring to an array of translations while we're here? One bullet would get extra APP_NAME but that would be ok

[aduth]

Hm, I like the idea. It's made complicated by the fact that these texts are reused for the "Delete Account" flow, where the second bullet point can have some variability.

identity-idp/app/views/users/delete/show.html.erb

Lines 10 to 13 in 48a6948

	<li class="margin-bottom-1"><%= t('users.delete.bullet_1', app_name: APP_NAME) %></li>
	<li class="margin-bottom-1"><%= current_user.decorate.delete_account_bullet_key %></li>
	<li class="margin-bottom-1"><%= t('users.delete.bullet_3', app_name: APP_NAME) %></li>
	<li class="margin-bottom-1"><%= t('users.delete.bullet_4', app_name: APP_NAME) %></li>

I'm not sure how best to handle that, or if it's worth the trouble to refactor it. I'll probably leave it out of this pull request though.