Add `fpm-server-requirement-status` E2E test (draft).

[techanvil]

Summary

Addresses issue:

• 9632

Relevant technical choices

This is an exploration of how we could provide E2E tests for the fpm-server-requirement-status. It's provided to capture the investigative work, however we should probably take an alternative approach, see https://github.com/google/site-kit-wp/issues/9708.

PR Author Checklist

• [ ] My code is tested and passes existing unit tests.
• [ ] My code has an appropriate set of unit tests which all pass.
• [ ] My code is backward-compatible with WordPress 5.2 and PHP 7.4.
• [ ] My code follows the WordPress coding standards.
• [ ] My code has proper inline documentation.
• [ ] I have added a QA Brief on the issue linked above.
• [ ] I have signed the Contributor License Agreement (see https://cla.developers.google.com/).

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Code Reviewer Checklist

• [ ] Run the code.
• [ ] Ensure the acceptance criteria are satisfied.
• [ ] Reassess the implementation with the IB.
• [ ] Ensure no unrelated changes are included.
• [ ] Ensure CI checks pass.
• [ ] Check Storybook where applicable.
• [ ] Ensure there is a QA Brief.
• [ ] Ensure there are no unexpected significant changes to file sizes.

Merge Reviewer Checklist

• [ ] Ensure the PR has the correct target branch.
• [ ] Double-check that the PR is okay to be merged.
• [ ] Ensure the corresponding issue has a ZenHub release assigned.
• [ ] Add a changelog message to the issue.