build(deps): bump the dependencies group across 1 directory with 6 updates

[dependabot]

Bumps the dependencies group with 4 updates in the /systemtest directory: go.opentelemetry.io/collector/pdata, go.yaml.in/yaml/v3, golang.org/x/net and google.golang.org/grpc.

Updates go.opentelemetry.io/collector/pdata from 1.61.0 to 1.63.0

Release notes

Sourced from go.opentelemetry.io/collector/pdata's releases.

v1.63.0/v0.157.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.157.0

End User Changelog

🛑 Breaking changes 🛑

• pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

• processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

• all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

• pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

  Example:

  service:
    telemetry:
      resource:
        attributes:
          - name: foo
            value: bar
        detection/development:

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/pdata's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

• pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

• pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

• pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

• pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.

v1.62.0/v0.156.0

🛑 Breaking changes 🛑

• pkg/pprofile: add bounds checks to FromAttributeIndices (#15517)

💡 Enhancements 💡

• cmd/mdatagen: Add field_name field to go_struct config in metadata.yaml to allow customizing the Go struct field name for generated config properties. (#15486)
• cmd/mdatagen: Handle enum validators in generated config structs (#14805) Supported validators include enum.
• cmd/mdatagen: Generate named Go types for primitive exported config schemas. (#15487) Primitive exported configs for string, integer, number, and boolean schemas now produce distinct exported types while default values and validation remain on referencing fields.

🧰 Bug fixes 🧰

• pkg/pprofile: fix wrong error sentinel in SetString (#15511)

Commits

• 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
• c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
• 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
• 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
• bd0d94a [configgrpc] Apply WaitForReady option (#15615)
• 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
• 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
• b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
• 2ab65ae [service] Record status events reported by extensions (#15557)
• fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
• Additional commits viewable in compare view

Updates go.yaml.in/yaml/v3 from 3.0.4 to 3.0.5

Commits

• e16c7af Remove empty go.sum file
• 6abcd01 Fix unhandled nil-errors in tests
• 9481db7 Remove suite_test.go and gopkg.in/check.v1
• 485f5fc Use standard testing library for limit_test.go
• 3e00046 Use standard testing library for node_test.go
• f612058 Use standard testing library for decode_test.go
• 078f958 Use standard testing library encode_test.go
• 3847ac0 [v3] backport CodeQL workflow
• 1666663 Revert incorrect gofmt changes
• 73290cb Retract v3 tags that cannot be installed
• See full diff in compare view

Updates golang.org/x/net from 0.56.0 to 0.57.0

Commits

• b8f09f6 go.mod: update golang.org/x dependencies
• f05f21b idna: reject all-ASCII xn-- labels on all Go versions
• 0f748cf internal/http3: clean up stream I/O methods usages in tests
• 0bb961e internal/http3: add net/http.ResponseController support
• 0ca694d webdav: document Dir's lack of defense against filesystem modification
• bd5f1dc http2: initialize Transport on NewClientConn
• 488ff63 bpf: add security considerations to package docs
• 93d1f25 xsrftoken: avoid token collisions
• 5a3baee internal/http3: prevent panic in QPACK decoder due to overflow
• See full diff in compare view

Updates golang.org/x/sync from 0.21.0 to 0.22.0

Commits

• 1eb64d4 semaphore: panic on negative weights
• See full diff in compare view

Updates golang.org/x/sys from 0.46.0 to 0.47.0

Commits

• 9e7e939 cpu: handle vendor suffixes in parseRelease
• f6fb8a1 unix: use epoll_pwait rather than epoll_wait
• f3eeabf windows: avoid length overflow in NewNTString
• 3cb6647 unix: update glibc to 2.43
• c507910 windows: document safe usage of TrusteeValue
• See full diff in compare view

Updates google.golang.org/grpc from 1.82.0 to 1.82.1

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.82.1

Security

• server: Stop reading from the connection when flooded by HTTP/2 frames. The default value for this limit is 100 frames, excluding DATA and HEADERS, and may be changed by setting environment variable GRPC_GO_EXPERIMENTAL_CONTROL_BUFFER_THROTTLE_LIMIT.
• xds/rbac: Support Metadata and RequestedServerName permissions matcher fields. If present in a DENY rule, previously these would be ignored and fail-open.
• xds/rbac: Fix panic when parsing unsupported fields in NotRule/NotId permissions.
• xds/rbac: Support the deprecated source_ip principal identifier by treating it as equivalent to direct_remote_ip.

Commits

• ebd8f06 Change version to 1.82.1 (#9238)
• 4ea465d Cherry-pick commits (#9236)
• 9494a2c Change version to 1.82.1-dev (#9171)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 9ff51c4

[mergify]

This pull request does not have a backport label. Could you fix it @dependabot[bot]? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8.19 is the label to automatically backport to the 8.19 branch.
• backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.