Exclude OpenTelemetry updates from the grouped weekly Renovate PR

[trask]

OpenTelemetry dependency updates now get their own Renovate pull request instead of being folded into the grouped weekly one. These updates drive dogfooding and cascaded releases across the OpenTelemetry Java repos, so holding them until Tuesday delays the release chain.

This affects io.opentelemetry.contrib:opentelemetry-aws-xray-propagator, io.opentelemetry.proto:opentelemetry-proto, and io.opentelemetry.semconv:opentelemetry-semconv-incubating.

OpenTelemetry-published Docker images such as otel/opentelemetry-collector-contrib stay grouped, since they are test infrastructure rather than part of a cascaded release.

[Copilot]

Pull request overview

This PR updates Renovate’s weekly “all patch and minor versions” grouping rule to ensure OpenTelemetry dependency updates are not batched, so they can land independently for dogfooding and cascaded releases.

Changes:

• Clarifies the grouping rule comment to reflect that it covers both patch and minor updates.
• Adds exclusions intended to keep OpenTelemetry artifacts and open-telemetry/** GitHub-sourced dependencies out of the grouped weekly PR.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[trask]

Closing this. opentelemetry-java sits at the root of the release chain, so nothing upstream of it has to cascade in here. Grouping OpenTelemetry updates into the weekly pull request, which is what this repo already does, is the right behavior.

The equivalent exclusion still applies in the downstream repos, where a delayed OpenTelemetry bump does hold up a cascaded release.