Boost: Add tracking events for cache related features

[dilirity]

One part of this, fixes #35275.

I wasn't sure if these should be on the PHP side when updating the data, so I left them in the UI. For setup, it was easiest to add it on the PHP side.

Proposed changes:

• Remove unnecessary event for UpgradeCTA component (we're rendering this multiple times on the page, and it doesn't make sense as users might not scroll to it);
• Add tracking events when updating bypass patterns and toggling logging;
• Add tracking events on setup failure (I thought it might be a good idea to see the most frequent issues users are facing).

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?

Not sure about this, as we're already tracking various aspects via Boost.

Testing instructions:

• Trigger cache setup errors and check for %cache_setup_error;
• Update bypass patterns and check for %update_cache_bypass_patterns;
• Toggle logging and check for %toggle_cache_logging.

[github-actions[bot]]

Thank you for your PR!

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

• :white_check_mark: Include a description of your PR changes.
  
• :white_check_mark: Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• :white_check_mark: Add testing instructions.
  
• :white_check_mark: Specify whether this PR includes any changes to data or privacy.
  
• :white_check_mark: 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 :robot:

---

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: April 2, 2024.
• Scheduled code freeze: March 25, 2024.

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

[haqadn]

Cherry-picked to 3.1.1 17e6f0f