Protect: Update Scan and History headers

[dkmyta]

Description

Updates the Scan and History header structure and content as per designs.

Note: This PR intentionally only address the above tasks, it does not add or remove any content and functionality for the existing UI. Bits and pieces may need addressing (or will be addressed) once the new ThreatsDataViews component is implemented in Protect.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

• https://github.com/Automattic/jetpack-scan-team/issues/1517

Does this pull request change what data or activity we track or use?

• No

Testing instructions:

• Use the Jetpack Beta Tester using this branch on Protect with a Scan upgrade
• Ensure the Scan header and the History header display as per designs (Note that you will need to manually visit /scan/history to view the History page as the navigation has been removed in preparation for ThreatsDataViews)
• Verify that the Show auto fixers button renders (when applicable - fixableThreatsList > 0) and on click displays the appropriate modal
• Ensure the onboarding popover for the above button renders accordingly
• Downgrade and ensure that appropriate content render for each
• Confirm no regressions are introduced

Screenshots

Scanner:

History:

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

---

Protect plugin:

• Next scheduled release: none scheduled.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[nateweller]

We should stack this on #40076 as it removes the scanner/history navigation from the header 👍

Will involve some breaking rebasing to do that, maybe we circle back after confirming the finalized designs this week?

[nateweller]

FYI: Stacked this on top of a project branch so we can merge.

LGTM 👍