feat: add automatic Docker service endpoint resolution

[briangreunke]

Add automatic Docker service endpoint resolution

Key Changes:

• Implement automatic endpoint resolution for Docker environments
• Add fallback strategies for containerized service discovery
• Enhance S3 filesystem connectivity in Docker deployments
• Improve error handling for network connectivity issues

Added:

• _resolve_endpoint() static method for endpoint resolution
• _is_docker_service_name() to detect Docker service names
• _resolve_docker_service() with multiple fallback strategies
• _test_connection() for socket-based connectivity testing
• Socket import for network connectivity checks

Changed:

• S3FileSystem initialization now uses resolved endpoints
• Enhanced error messages for connection failures
• Improved Docker service name detection logic
• Updated endpoint handling in configure() method

Removed:

• N/A

---

Generated Summary:

• Introduced automatic resolution of endpoint URLs based on environment and Docker settings.
• Added three static methods:
  • _resolve_endpoint: Resolves the provided endpoint URL.
  • _is_docker_service_name: Detects if a hostname is a Docker service name.
  • _resolve_docker_service: Attempts to resolve service name to actual address using multiple strategies.
  • _test_connection: Conducts a simple connectivity test on the given endpoint.
• Updated the configure method to use the new endpoint resolution logic when connecting to S3 storage.
• Potential impact:
  • Improves connectivity handling for Dockerized environments.
  • Provides clearer error messaging on connection failures.
  • Enhances flexibility for deploying across different infrastructures.

This summary was generated with ❤️ by rigging

This PR addresses connectivity issues when running Dreadnode in Docker environments where service names need to be resolved to accessible endpoints. The implementation tries multiple resolution strategies (original service name, localhost, host.docker.internal, Docker bridge IP) and automatically selects the first working connection.