Group otel dependencies in a single dependabot PR (#935)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR groups all otel deps in a single dependabot PR as
usually they are spread across 4-5 separate ones whenever there's a new
version.

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

.github/dependabot.yml

@@ -2,10 +2,18 @@ version: 2
 updates:
   - package-ecosystem: gomod
     directory: /
+    groups:
+      opentelemetry:
+        patterns:
+          - "go.opentelemetry.io/*"
     schedule:
       interval: daily
   - package-ecosystem: gomod
     directory: /deploy
+    groups:
+      opentelemetry:
+        patterns:
+          - "go.opentelemetry.io/*"
     schedule:
       interval: daily
   - package-ecosystem: github-actions