Allow disabling (most of) CI with no-test label

[dhruvmanila]

Ref: astral-sh/uv#9456

[MichaReiser]

I don't mind the change if other people find it useful, but I worry that it adds complexity to our CI jobs without being used much because it requires an extra label. I'm probably too lazy to add it, and not adding it has no actual cost to me. Would it make more sense to automatically apply the new behavior to draft PRs unless they have a specific label? Draft PRs already express the I'm not done yet without requiring an extra step from my side (and the gh CLI makes it very easy to publish in draft, publishing with a label is a bit more involved)

[dhruvmanila]

Would it make more sense to automatically apply the new behavior to draft PRs unless they have a specific label because draft PRs already express the: I'm not done here.

Yeah, I think I'm more in favor of checking the draft status of the PR instead of label. I've asked @zanieb for their opinion on this, will wait until then. I'm happy to hear others opinion as well.

[AlexWaygood]

One of the reasons I sometimes open draft PRs is to e.g. check it passes all CI before requesting the review of codeowners. Most CI can be run locally, it's true, but for some CI jobs it's much easier to just see how it does on GitHub (e.g. the ecosystem checks). So I'm not sure I'd be a huge fan of auto-disabling all CI for draft PRs.