Protect: Add WAF header stat cards

[dkmyta]

Description

Adds StatCard components to the FirewallHeader

Changes proposed in this Pull Request:

• Makes the StatCard component a default js-packages component export
• Applies the StatCard component to the FirewallHeader
• Retrieves and display WAF blocked requests when applicable

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

• 1202232924268038-as-1203282049665710

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

• No

Testing instructions:

• Checkout this branch
• Start your Jurassic Tube without a scan level upgrade on a site with a history of blocked requests
• Activate Protect and proceed to the Firewall tab
• Ensure that the StatCard components are disabled, display the placeholder value, and a "Paid feature" label
• Upgrade your plan
• Return the Firewall page and verify that the StatCard components are now active and display an appropriate value for each period
• Switch to mobile view and ensure that the structure and styling line up with the provided designs
• Verify that there is no regression in app functionality introduced

Screenshots

Disabled:

Active:

Mobile:

[github-actions]

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run

bin/jetpack-downloader test jetpack add/protect-waf-stat-cards

to get started. More details: p9dueE-5Nn-p2

[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.
  
• ⚠️ All commits were linted before commit.
  
• ✅ 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.

---

🔴 Action required: Please add missing changelog entries for the following projects: projects/packages/waf, projects/plugins/protect

Use the Jetpack CLI tool to generate changelog entries by running the following command: jetpack changelog add.
Guidelines: /docs/writing-a-good-changelog-entry.md

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

---

Protect plugin:

• Next scheduled release: March 7, 2023.
• Scheduled code freeze: February 27, 2023.