Type of Change

• New Feature
• Bug Fix
• Documentation
• Performance Improvement
• Test/CI
• Refactor
• Other:

Related Issues

Summary of Changes

chore: bump dependencies, add metrics support, remove DNS resolver

• Bump multiple crate versions to latest compatible releases to address security
  fixes and dependency drift. Ran cargo update and adjusted code for minor
  API changes where required.

• Introduce metrics collection via the metrics crate:

  • Add metrics dependency and initialize basic metrics plumbing.
  • Instrument critical S3 operations (create_bucket, put_object, copy_object,
    delete_object, multipart operations, etc.) with counters and key metrics.
  • Ensure metrics initialization is safe for global use (avoid leaking &str
    lifetimes and OnceCell invariants).

• Remove custom DNS resolver feature:

  • Delete resolver implementation and related configuration/options.
  • Remove associated dependencies and tests relying on custom resolver.
  • Fall back to system resolver behavior; update docs/config to reflect this.

• Fixes and tidy-ups:

  • Resolve lifetime/ownership issues introduced by telemetry/global state
    initialization (avoid Box::leak and static reference escapes).
  • Update imports/usages impacted by dependency bumps.
  • Add/adjust unit tests where feasible and update CI to reflect changed deps.

BREAKING CHANGES:

• Custom DNS resolver removed. Users relying on resolver-specific config must
  migrate to system DNS or reintroduce a resolver implementation.
• Telemetry initialization now uses owned/static-safe values; code that relied
  on leaked &'static strings should be updated.

Migration notes:

• Run cargo update then cargo build to apply dependency changes.
• Review configuration for DNS resolver entries and remove or replace them.
• Ensure metrics backend is configured (e.g. exporter or aggregator) if you
  expect metrics to be exported.

Checklist

• I have read and followed the CONTRIBUTING.md guidelines
• Passed make pre-commit
• Added/updated necessary tests
• Documentation updated (if needed)
• CI/CD passed (if applicable)

Impact

• Breaking change (compatibility)
• Requires doc/config/deployment update
• Other impact:

Additional Notes

Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.