Investigate why container agent does not check in when created from patch

Task ID: evg_lint_generate_lint_patch_353be1934dd2fe13f111bdf94c907f0e606b0385_62b4a1679dbe323902b0b330_22_06_23_17_23_06

Pod ID: 62b4a762a09b5cc4a16ed93e

This came out of the e2e testing. When a pod is created from the POC's REST route, it can successfully connect to the Evergreen application server, request the agent setup data, and ask for the next task. However, when the pod is created from a task, the container remains in the "RUNNING" state forever without checking into the application srever. Investigation using an interactive shell session suggests that the agent is running and producing logs but there's no indication that it attempts to make a request to the Evergreen app server.

We should investigate what exactly is different between the POC REST route and the patch that makes it so that the REST route's pod can connect but the task's pod cannot. Should especially investigate if the pod definitions are different in some way (especially networking).