[LHDM-2201] Header/Footer Custom classes/IDs

[seesleestak]

Summary

• Our team has a specific Smartling-related requirement to be able to assign class names and IDs to the logo, language switch link, and log in link in the Header and the logo in the Footer.
• https://jira.cms.gov/browse/LHDM-2201

How to test

For testing, I'd added props for all the ids/classes on a storybook story to verify

export const LoggedOutHeader: Story = {
  args: {
    customIds: {
      headerLogo: 'custom-header-id',
      languageLink: 'custom-language-link-id',
      loginLink: 'custom-language-login-id',
    },
    customClassNames: {
      headerLogo: 'custom-header-class',
      languageLink: 'custom-language-link-class',
      loginLink: 'custom-language-login-class',
    }
  },
};

Checklist

• Prefixed the PR title with the Jira ticket number as [WNMGDS-####] Title or [NO-TICKET] if this is unticketed work.
• Selected appropriate Type (only one) label for this PR, if it is a breaking change, label should only be Type: Breaking
• Selected appropriate Impacts, multiple can be selected.
• Selected appropriate release milestone

If this is a change to design:

• If visual regression image references have been changed, design MUST be assigned to review. In this instance, designer approval is a requirement before the PR can be merged.

If this is a change to code:

• Created or updated unit tests to cover any new or modified code
• If necessary, updated unit-test snapshots (yarn test:unit:update) and browser-test snapshots (yarn test:browser:update)

If this is a change to documentation:

• Checked for spelling and grammatical errors

[seesleestak]

I ran yarn test:browser:update but the changes I saw locally didn't seem related to the PR changes or the build error. Any help deciphering that would be appreciated.