Boost: Update e2e tests to account for lazy loading removal

[dilirity]

Jetpack removed lazy loading, so these tests have been trimmed down
because of that.
Since our module is disabled by default and can not be activated,
it shouldn't be activatable.

Proposed changes:

• Fixes e2e tests related to recent lazy loading updates. Since the module is now visible in the UI but can not be activated, the tests now accommodate for that.

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

n/a

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

no

Testing instructions:

• Checkout this version of Boost;
• Run e2e tests - they should all pass (hopefully no tunnel issues).

[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.

---

Once your PR is ready for review, check one last time that all required checks 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 reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

---

Boost plugin:

• Next scheduled release: December 5, 2023.
• Scheduled code freeze: November 27, 2023.

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

[haqadn]

Thanks for looking into it. I think we should not have any lazy loading tests since currently it depend on too many variables like WP 6.4, Gutenberg 16.6.0. I think it will just add to the current flakyness of the tests.

[haqadn]

Thank you for taking care of this. Looks like we may need add more tests since we have added new features in Boost.