feat: find ways to improve docker experience of keploy.

Currently, we follow specific instructions to run Keploy in a Docker environment:

1. Adding Delay in User Application: For fast applications like Golang, we introduce a delay to capture the PID of the container. This PID is crucial for obtaining the PID namespace (inode) and sending it to the kernel space via eBPF maps. The inode can only be extracted once the PID is known, which requires the container to be running. However, the application starts immediately upon container execution, causing us to miss some initial external service calls. These initial calls are crucial because the application maintains connection pooling. But they get filtered as we couldn't identify the application-related calls on time.
2. TLS Support in Docker: To support TLS in a Docker environment, we currently require users to add a script in the application Dockerfile to inject our custom CA into the application's Docker container. It would be beneficial if Keploy could handle this process internally without needing an external script.
3. DNS Issues in Docker: There are DNS-related issues in the Docker environment where certain hooks fail to capture DNS calls. This leads to unresolved DNS queries, particularly in older Linux distributions. Addressing this issue is crucial as it significantly impacts the reliability of the application.

Solving this issue can automatically help us in resolving the above-mentioned issues.

The issue identifies Docker startup and PID capture, TLS CA injection, and DNS hooks as the areas to investigate; no repository files or tests are named. Begin by tracing the Docker/eBPF capture path and reviewing issue #645, then define success as capturing initial pooled calls, supporting TLS without an application script, and resolving DNS calls in affected distributions.