Remove remoteaddr to reduce attribute cardinality

[youngbupark]

Description

otelhttp has the high cardinality problem which record all remote address from client. This issue is tracked by open-telemetry/opentelemetry-go-contrib#3765 .

This PR is adding workaround to prevent otelhttp from recording remoteaddr as an attribute.

Issue reference

#5299
#5237

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Adds necessary unit tests for change
• Adds necessary E2E tests for change
• Unit tests passing
• Extended the documentation / Created issue for it

[youngbupark]

There is the similar problem due to the high cardinality from remoteaddr port : open-telemetry/opentelemetry-go#3765

[github-actions]

Test Results

2 514 tests  ±0   2 507 ✔️ ±0   1m 57s ⏱️ +2s
   230 suites ±0          7 💤 ±0 
       1 files   ±0          0 ❌ ±0 

Results for commit cb232fe. ± Comparison against base commit 42a6f1b.

This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.

github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/430687f4-6faf-424d-a547-95efbaa122ba
github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/430687f4-6faf-424d-a547-95efbaa122ba#01

github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/df3c3c7c-7f3b-4d47-a740-33e00cfd167c
github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/df3c3c7c-7f3b-4d47-a740-33e00cfd167c#01

♻️ This comment has been updated with latest results.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[vinayada1]

Do we need these package version changes?

[youngbupark]

Yes. these are all related :)

[ytimocin]

There is just one small typo but other than that LGTM

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[youngbupark]

@vinayada1 Once you validate the change, please approve this pr :)

[vinayada1]