chore(deps): Update debian image usages to trixie

[dratasich]

Summary

Debian 13 trixie was released Aug, 9th.

This should fix some vulnerabilities when using the docker debian image and also update some libs.

I've used str-replace and checked/aligned to the changes in PR #18057 from @jszwedko - Thanks!
Please feel free to commit on top or submit your own PR in case this misses a lot and/or I lack of quick responses ;)

Vector configuration

cat vector.test.toml

[api]
enabled = true
address = "0.0.0.0:8686"

[sources.in]
type = "http_server"
address = "0.0.0.0:8080"
path = "/logs"

[sinks.out]
inputs = ["in"]
type = "console"
encoding.codec = "text"

How did you test this PR?

$ docker build -f regression/Dockerfile -t vector:trixie .
$ docker run --rm vector:trixie --version
vector 0.50.0 (x86_64-unknown-linux-gnu)

With above minimalistic vector config vector.test.toml, start image and send a post request to log curl -X POST localhost:8080/logs -d '{"test": true}':

$ docker run -i -v $(pwd):/etc/vector/ -p 8080:8080 -p 8686:8686 --rm vector:trixie --config /etc/vector/vector.test.toml
2025-09-04T06:00:18.831303Z  INFO vector::app: Log level is enabled. level="info"
2025-09-04T06:00:18.831861Z  INFO vector::app: Loading configs. paths=["/etc/vector/vector.test.toml"]
2025-09-04T06:00:18.833809Z  INFO vector::topology::running: Running healthchecks.
2025-09-04T06:00:18.833907Z  INFO vector: Vector has started. debug="false" version="0.50.0" arch="x86_64" revision=""
2025-09-04T06:00:18.833905Z  INFO vector::topology::builder: Healthcheck passed.
2025-09-04T06:00:18.834023Z  INFO source{component_kind="source" component_id=in component_type=http_server}: vector::sources::util::http::prelude: Building HTTP server. address=0.0.0.0:8080
2025-09-04T06:00:18.834894Z  INFO vector::internal_events::api: API server running. address=0.0.0.0:8686 playground=http://0.0.0.0:8686/playground graphql=http://0.0.0.0:8686/graphql
{"test": true}
^C2025-09-04T06:00:23.584817Z  INFO vector::signal: Signal received. signal="SIGINT"
2025-09-04T06:00:23.584871Z  INFO vector: Vector has stopped.

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • cargo fmt --all
    • cargo clippy --workspace --all-targets -- -D warnings
    • cargo nextest run --workspace (alternatively, you can run cargo test --all)
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run cargo vdev build licenses to regenerate the license inventory and commit the changes (if any). More details here.

[pront]

Thank you @dratasich!