feat(initial submission): Set up New Submission triage options

[hannasage]

Purpose

This PR adds in the triage of navigation options for the New Submission screen, so a user can select the authority type, document type, and navigate to the desired page.

NOTE: The only functional one is SPA > Medicaid SPA which will link to our current dummy form for facilitating development.

Linked Issues to Close

https://qmacbis.atlassian.net/browse/OY2-25391

Approach

We have a single component that acts as a reusable page (OptionsPage) made of sub-components that handle styling. Each route links to a specific instance of the OptionsPage fed with different OptionData values. These values dictate the title, description, and path linked to.

Let's say you arrive at /new-submission, this is what powers the page of initial options:

export const NewSubmissionInitialOptions = () => (
    <OptionsPage
        title="Submission Type"
        fieldsetLegend="Select a Submission Type"
        options={AUTHORITY_OPTIONS}
    />
);

And this will be one of your options:

{
    title: "State Plan Amendment (SPA)",
    description: "Submit a Medicaid or CHIP State Plan Amendment",
    linkTo: ROUTES.SPA_SUBMISSION_OPTIONS
}

The above example links to /new-submission/spa, and on that page, we render:

export const SPASubmissionOptions = () => (
    <OptionsPage
        title="SPA Type"
        fieldsetLegend="Select a SPA type to start your submission"
        options={SPA_OPTIONS} />
);

which will have subsequent options with subsequent links.

The router includes the following to wire this up:

{ path: ROUTES.NEW_SUBMISSION_OPTIONS, element: <P.NewSubmissionInitialOptions /> },
{ path: ROUTES.SPA_SUBMISSION_OPTIONS, element: <P.SPASubmissionOptions /> },

Assorted Notes/Considerations/Learning

I fixed up the CardWithTopBorder styles a bit. The gradient bar wasn't rounded, and the border was overlapping it a bit, so I yanked some of the styles from OneMAC to patch it up and added padding back where necessary, hence some seemingly rogue changes in the PR (faq and description used the component)

[hannasage]

To prevent circular imports between router.tsx and the components/pages using ROUTES, they've been broken out into their own file -- this can be something of an "all constants" file in the future if we need it. Without this separation, the circular dependency between files leads to an undefined error when importing and using the constant values.

[hannasage]

https://dmyvu7iwkchj7.cloudfront.net/

[benjaminpaige]

semantic html, routing consts, unit tests, inline comments and a thorough pr write up... oh my good heavens!

[github-actions]

🎉 This PR is included in version 1.5.0-val.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀