HOTFIX - TMEDIA-495 Horizontal Links Defect

[matthewroach]

Description

Update the CSS to fix the specificity with the updates to parent components now being Styled Components

https://styled-components.com/docs/advanced#issues-with-specificity

Jira Ticket

• TMEDIA-495

Test Steps

• Add test steps a reviewer must complete to test this PR

1. Checkout this branch git checkout TMEDIA-495-horizontal-links
2. Run fusion repo with linked blocks npx fusion start -f -l @wpmedia/header-nav-chain-block
3. Navigate to the homepage - http://localhost/homepage/?_website=the-gazette
4. Validate the horizontal links in the header nav chain
   • are visible on desktop viewport
   • are not shown on non desktop viewports

Effect Of Changes

Before

After

Author Checklist

The author of the PR should fill out the following sections to ensure this PR is ready for review.

• Confirmed all the test steps a reviewer will follow above are working.
• Confirmed there are no linter errors. Please run npm run lint to check for errors. Often, npm run lint:fix will fix those errors and warnings.
• Ran this code locally and checked that there are not any unintended side effects. For example, that a CSS selector is scoped only to a particular block.
• Confirmed this PR has reasonable code coverage. You can run npm run test:coverage to see your progress.
  • Confirmed this PR has unit test files
  • Ran npm run test, made sure all tests are passing
  • If the amount of work to write unit tests for this change are excessive,
    please explain why (so that we can fix it whenever it gets refactored).
• Confirmed relevant documentation has been updated/added.

Reviewer Checklist

The reviewer of the PR should copy-paste this template into the review comments on review.

• Linting code actions have passed.
• Ran the code locally based on the test instructions.
  • I don’t think this is needed to be tested locally. For example, a padding style change (storybook?) or a logic change (write a test).
• I am a member of the engine theme team so that I can approve and merge this. If you're not on the team, you won't have access to approve and merge this pr.
• Looked to see that the new or changed code has code coverage, specifically. We want the global code coverage to keep on going up with targeted testing.

[JackHowa]

Working as expected in my testing; nice work

after:

before: