test: no-op CI baseline probe (do not merge)

[Eddcapone]

Diagnostic-only PR - adds a single new markdown file, no code changes.

Purpose: confirm whether the Unit Tests / Functional Tests CE failures
seen on #41152 are pre-existing CI infrastructure flakiness rather than
caused by that PR's diff. Branched directly from magento/magento2's
2.4-develop tip.

Not intended to be merged.

[m2-assistant]

Hi @Eddcapone. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[Eddcapone]

@magento run all tests