Wire Maestro smoke tests into Buildkite

[JorgeMucientes]

Description

Adds Buildkite entry points for Maestro smoke testing.

This final stack layer wires the local runner into Buildkite with a manual pipeline step, a release-pipeline command, and a scheduled burst pipeline. CI execution remains explicit and tag-driven, while artifacts are uploaded from the runner output directory for review.

Stack navigation: previous #16256

Test Steps

1. In Buildkite, trigger the manual Maestro smoke test step with the desired tag/store settings.
2. Confirm the command runs .buildkite/commands/run-maestro-tests.sh.
3. Confirm the HTML/JUnit artifacts are uploaded from WooCommerce/build/outputs/maestro-smoke.

Images/gif

N/A

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

[dangermattic]

	1 Message
📖	This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Platform	📱 Mobile
	Flavor	Jalapeno
	Build Type	Debug
	Build Number	766
	Version	25.1-rc-1
	Application ID	com.woocommerce.android.prealpha
	Commit	35c50fb
	Installation URL	5or8ulk008prg

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

Version 25.2 has now entered code-freeze, so the milestone of this PR has been updated to 25.3.