Remove uswds from mhv-landing-page components after v3 update

[jzucadi]

The design team will be upgrading all web-component to their V3 versions. This PR updates the current va components to their v3 versions.

The following files were updated:

Related issue(s)

Slack message from #vfs-change-announcements

Tasks

• Manually remove uswds to all web-component instances in mhv-landing-page.

Acceptance criteria

• Update every component to not have USWDS prop as v3 update will set this true by default

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

[micahchiang]

Requesting changes for now. There's nothing wrong with this PR, we haven't been able to merge our design system PR into vets website yet, so I don't want you to merge this early and then be left waiting.

Design system upgrade to v3 has been merged