[resourcedetectionprocessor] Update README for AWS detector when instance is part of AWS Parallel Cluster

[dloucasfx]

Description:

Was debugging an issue where OTEL was failing to connect to the AWS metadata server, whereas manual curl was working.
However, running the curl command as the user running the OTEL process failed

su -s /bin/bash -c 'curl http:https://169.254.169.254/latest/meta-data/instance-id' <otel_user>

it turns out the EC2 instance in question is a node in a "parallel cluster" and AWS is adding an IPtable rule to block access to the metadata server and only allow it for root and 2 other users.

-A PARALLELCLUSTER_IMDS -d 169.254.169.254/32 -m owner --uid-owner 0 -j ACCEPT
-A PARALLELCLUSTER_IMDS -d 169.254.169.254/32 -m owner --uid-owner 400 -j ACCEPT
-A PARALLELCLUSTER_IMDS -d 169.254.169.254/32 -m owner --uid-owner 1000 -j ACCEPT
-A PARALLELCLUSTER_IMDS -d 169.254.169.254/32 -j REJECT --reject-with icmp-port-unreachable

https://github.com/aws/aws-parallelcluster-cookbook/blame/develop/cookbooks/aws-parallelcluster-config/files/default/imds/imds-access.sh#L105

Adding a rule to PARALLELCLUSTER_IMDS to allow <otel_user> access to the metadata server fixed the issue.

This PR improves the readme and cover this use case
Link to tracking Issue:

Testing:

Documentation:
README updated

[runforesight]

Foresight Summary

    
Major Impacts

build-and-test-windows duration(8 seconds) has decreased 30 minutes 36 seconds compared to main branch avg(30 minutes 44 seconds).

View More Details

⭕  changelog workflow has finished in 6 seconds (2 minutes 9 seconds less than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
changelog	-     🔗	N/A	See Details

---

⭕  build-and-test-windows workflow has finished in 8 seconds (30 minutes 44 seconds less than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
windows-unittest-matrix	-     🔗	N/A	See Details
windows-unittest	-     🔗	N/A	See Details

---

✅  telemetrygen workflow has finished in 1 minute 18 seconds and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
build-dev	-     🔗	N/A	See Details
publish-latest	-     🔗	N/A	See Details
publish-stable	-     🔗	N/A	See Details

---

✅  check-links workflow has finished in 1 minute 46 seconds (⚠️ 47 seconds more than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
changed files	-     🔗	N/A	See Details
check-links	-     🔗	N/A	See Details

---

✅  prometheus-compliance-tests workflow has finished in 3 minutes 2 seconds (3 minutes 16 seconds less than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
prometheus-compliance-tests	-     🔗	N/A	See Details

---

✅  load-tests workflow has finished in 6 minutes 45 seconds (3 minutes 35 seconds less than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
setup-environment	-     🔗	N/A	See Details
loadtest (TestIdleMode)	-     🔗	N/A	See Details
loadtest (TestBallastMemory|TestLog10kDPS)	-     🔗	N/A	See Details
loadtest (TestMetric10kDPS|TestMetricsFromFile)	-     🔗	N/A	See Details
loadtest (TestMetricResourceProcessor|TestTrace10kSPS)	-     🔗	N/A	See Details
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs)	-     🔗	N/A	See Details
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs)	-     🔗	N/A	See Details
loadtest (TestTraceAttributesProcessor)	-     🔗	N/A	See Details

---

✅  e2e-tests workflow has finished in 11 minutes 2 seconds (3 minutes 3 seconds less than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
kubernetes-test (v1.26.0)	-     🔗	N/A	See Details
kubernetes-test (v1.25.3)	-     🔗	N/A	See Details
kubernetes-test (v1.24.7)	-     🔗	N/A	See Details
kubernetes-test (v1.23.13)	-     🔗	N/A	See Details

---

✅  build-and-test workflow has finished in 35 minutes 32 seconds (11 minutes 5 seconds less than main branch avg.) and finished at 10th Apr, 2023.

---

Job	Failed Steps	Tests
setup-environment	-     🔗	N/A	See Details
build-examples	-     🔗	N/A	See Details
check-collector-module-version	-     🔗	N/A	See Details
checks	-     🔗	N/A	See Details
check-codeowners	-     🔗	N/A	See Details
correctness-metrics	-     🔗	N/A	See Details
correctness-traces	-     🔗	N/A	See Details
integration-tests	-     🔗	N/A	See Details
lint-matrix (receiver-0)	-     🔗	N/A	See Details
lint-matrix (receiver-1)	-     🔗	N/A	See Details
lint-matrix (processor)	-     🔗	N/A	See Details
lint-matrix (exporter)	-     🔗	N/A	See Details
lint-matrix (extension)	-     🔗	N/A	See Details
lint-matrix (connector)	-     🔗	N/A	See Details
lint-matrix (internal)	-     🔗	N/A	See Details
lint-matrix (other)	-     🔗	N/A	See Details
unittest-matrix (1.20, receiver-0)	-     🔗	N/A	See Details
unittest-matrix (1.20, receiver-1)	-     🔗	N/A	See Details
unittest-matrix (1.20, processor)	-     🔗	N/A	See Details
unittest-matrix (1.20, exporter)	-     🔗	N/A	See Details
unittest-matrix (1.20, extension)	-     🔗	N/A	See Details
unittest-matrix (1.20, connector)	-     🔗	N/A	See Details
unittest-matrix (1.20, internal)	-     🔗	N/A	See Details
unittest-matrix (1.20, other)	-     🔗	N/A	See Details
unittest-matrix (1.19, receiver-0)	-     🔗	N/A	See Details
unittest-matrix (1.19, receiver-1)	-     🔗	N/A	See Details
unittest-matrix (1.19, processor)	-     🔗	N/A	See Details
unittest-matrix (1.19, exporter)	-     🔗	N/A	See Details
unittest-matrix (1.19, extension)	-     🔗	N/A	See Details
unittest-matrix (1.19, connector)	-     🔗	N/A	See Details
unittest-matrix (1.19, internal)	-     🔗	N/A	See Details
unittest-matrix (1.19, other)	-     🔗	N/A	See Details
lint	-     🔗	N/A	See Details
unittest (1.20)	-     🔗	N/A	See Details
unittest (1.19)	-     🔗	N/A	See Details
cross-compile (darwin, amd64)	-     🔗	N/A	See Details
cross-compile (darwin, arm64)	-     🔗	N/A	See Details
cross-compile (linux, 386)	-     🔗	N/A	See Details
cross-compile (linux, amd64)	-     🔗	N/A	See Details
cross-compile (linux, arm)	-     🔗	N/A	See Details
cross-compile (linux, arm64)	-     🔗	N/A	See Details
cross-compile (linux, ppc64le)	-     🔗	N/A	See Details
cross-compile (windows, 386)	-     🔗	N/A	See Details
cross-compile (windows, amd64)	-     🔗	N/A	See Details
build-package (deb)	-     🔗	N/A	See Details
build-package (rpm)	-     🔗	N/A	See Details
windows-msi	-     🔗	N/A	See Details
publish-check	-     🔗	N/A	See Details
publish-stable	-     🔗	N/A	See Details
publish-dev	-     🔗	N/A	See Details
rotate-milestone	-     🔗	N/A	See Details

---

🔎 See details on Foresight

^{*You can configure Foresight comments in your organization settings page.}

[atoulme]

LGTM - maybe there's no need to have a changelog entry, in which case you can add [chore] to the PR title or add the "Skip Changelog" label.

[dmitryax]

Please remove the changelog entry. It's not needed for documentation updates. I added "Skip changelog" label to pass CI