Protect: Fix checks for paid plan

[nateweller]

Changes proposed in this Pull Request:

• We've been having reliability issues using Scan::has_required_plan() from My_Jetpack due to server timeouts, this PR introduces a new way of validating the site plan using the connection package's Current_Plan. While the My Jetpack method validates the plan by availability of an accessible scan status, this alternate method directly checks the site's available features. This allows us to handle scenarios where the site has the correct plan, but no available scan status (i.e. right after purchase, the scanner may still be initializing and is "unavailable" for a few moments.)
• This PR also updates what logic is ran by protect on the init hook, moving any code that relies on status data to _admin_menu, where it will be called only when necessary instead of every page load.

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?

Jetpack product discussion

1201069996155224-as-1203341574761584

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

No

Testing instructions:

• Start up a JN site with Jetpack Beta running this branch for Protect, and no core Jetpack plugin installed.
• Go through the process of activating Protect as a paid and free user, validating both experiences use the proper UI and status data source.
• Manually upgrade or cancel your plan outside of wp-admin, and validate the correct plan is immediately recognized in Protect.

[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/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: December 6, 2022.
• Scheduled code freeze: November 28, 2022.

[dkmyta]

This is a major improvement - awesome work!