Track prepare-campaign server telemetry (ADS-1041)

[j6ll]

Proposed changes

Adds server-side Tracks telemetry around the Blaze prepare-campaign MCP flow so we can observe tool usage and generated prefill outcomes.

Stacked on #48604.

Testing

• pnpm exec jetpack test php packages/blaze
• composer phpcs:lint projects/packages/blaze/src/abilities/class-blaze-abilities.php projects/packages/blaze/src/class-campaign-preparer.php projects/packages/blaze/tests/php/abilities/Blaze_Abilities_Test.php projects/packages/blaze/tests/php/Campaign_Preparer_Test.php
• tools/check-changelogger-use.php --debug origin/trunk HEAD
• tools/changelogger-validate-all.sh -vv

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the add/ads-1041-prepare-campaign-telemetry branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/ads-1041-prepare-campaign-telemetry

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/ads-1041-prepare-campaign-telemetry

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-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.
  
• 🔴 Add a "[Status]" label (In Progress, Needs 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 🤖

---

🔴 Action required: Please include detailed testing steps, explaining how to test your change, like so:

## Testing instructions:

* Go to '..'
*

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

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

My PR adds *x* and *y*.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

No summary data is available for parent commit 0082a93, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for 0082a93 is available.

Full summary · PHP report · JS report