Fixed Agent crashing in AWS Fargate

[Akshay2191]

Currently, the Agent fails to start in AWS Fargate environments. This occurs because Fargate abstracts the host filesystem, causing traditional container ID retrieval methods—which rely on specific /proc/self/mountinfo formats or the presence of standard Docker files—to return empty values. Without a valid Container ID, the Agent cannot unique identify itself to the NGINX One console and terminates.

As a fix, the Agent now detects the Fargate runtime and utilizes the AWS Metadata Endpoint to reliably retrieve the container ID.

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 15 lines in your changes missing coverage. Please review.
✅ Project coverage is 85.06%. Comparing base (5df1f54) to head (d02a2ac).
⚠️ Report is 6 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/host/info.go	66.66%	11 Missing and 4 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1493      +/-   ##
==========================================
- Coverage   85.10%   85.06%   -0.04%     
==========================================
  Files         102      102              
  Lines       12992    13255     +263     
==========================================
+ Hits        11057    11276     +219     
- Misses       1448     1485      +37     
- Partials      487      494       +7     

Files with missing lines	Coverage Δ
pkg/host/info.go	76.11% <66.66%> (-3.03%)	⬇️

... and 20 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d95d70...d02a2ac. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.