Add no-op test + check workflow

[penalosa]

What this PR solves / how to test

Fixes #6685

Reduce wasted CI time by adding no-op workflows for tests and pre-releases that run when a PR only touches markdown files. We need a no-op workflow rather than just skipping the jobs because both tests and pre-releases are required workflows for a PR to be merged.

You can see the result of these changes on this example PR: #6681

Author has addressed the following

• Tests
  • TODO (before merge)
  • Included
  • Not necessary because: workflows change
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required / Maybe required
  • Not required because: doesn't touch package code
• Changeset (Changeset guidelines)
  • TODO (before merge)
  • Included
  • Not necessary because: no releases should be triggered
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Not necessary because: internal detail

[changeset-bot]

⚠️ No Changeset found

Latest commit: fc12d23

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-wrangler-6682

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6682/npm-package-wrangler-6682

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-wrangler-6682 dev path/to/script.js

Additional artifacts:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-create-cloudflare-6682 --no-auto-update

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-cloudflare-kv-asset-handler-6682

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-miniflare-6682

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-cloudflare-pages-shared-6682

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-cloudflare-vitest-pool-workers-6682

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-cloudflare-workers-editor-shared-6682

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/10821206001/npm-package-cloudflare-workers-shared-6682

Note that these links will no longer work once the GitHub Actions artifact expires.

---

[email protected] includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20240821.2
workerd	1.20240909.0	1.20240909.0
workerd --version	1.20240909.0	2024-09-09

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[petebacondarwin]

What happens if both markdown and non-markdown are touched?
Will we end up with two CI jobs with the same name running?
How does that affect the required checks?

[penalosa]

Closing in favour of #6770