Landing page and secondary nav links handle new root font size

[wesrowe]

Description

User story

As a Cartography team member, I want to ensure that the updated root font sizes of the VADS don't change the size of fonts on the MHV landing page, so that Veterans' experience is unchanged.

Notes

• Platform announcement of change in style and why it shouldn't affect apps
• VADS PR linked from that announcement
• slack - Daniel's analysis of why
• Updates should be merged into department-of-veterans-affairs/vets-website/pull/26606 before it goes live
  • Team to ask DST if they agree with us updating their PR

Possible tasks:

Acceptance criteria

• The MHV landing page is styled such that the VADS's tweaks in their PR don't cause a visible change for even a second
• Same for MHV secondary nav component
• QA review

[dcloud]

We may also need to tweak rem values in Secondary Nav, as mentioned on department-of-veterans-affairs/vets-website/pull/29592

[dcloud]

Looks like the landing page changes exist in the big PR now: https://github.com/department-of-veterans-affairs/vets-website/pull/26606/files?show-viewed-files=true&file-filters%5B%5D=#diff-3eb65c1def06b4b948dd2d4ffc6cc930ec11fda40bd770611d62866f4b1e8c3c

Things under src/platform/mhv, e.g. Secondary Nav, appear uncoverted at this time

[dcloud]

Created a PR pointing to the bigger PR, and left a review comment asking for those minor changes

[dcloud]

The Secondary Nav changes are merged into the larger PR, department-of-veterans-affairs/vets-website/pull/26606, and I have review typography/spacing changes on that branch and things look good.

I think this is done as far as we are concerned, but I don't know the ETA for when the bigger PR will get merged

[dcloud]

The larger PR has been merged