feat: OpenTelemetry standard attributes

[pablocarle]

Description

Implementation of required / additional / recommended properties for base signals from APIML OpenTelemetry implementation with defaults.

Linked to # (issue)
Part of the # (epic)

Type of change

• feat: New feature (non-breaking change which adds functionality)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

[richard-salac]

This method is executed and values generated, but are overridden later.
See io/opentelemetry/sdk/autoconfigure/ResourceConfiguration.java:100

There are multiple resource providers available and our values get overridden. The spi helper loads the providers and orders them.

We need 2 things:

• our provider must set order to make sure our provider comes last, see io.opentelemetry.sdk.autoconfigure.spi.Ordered#order
• we need to add an acceptance test

[pablocarle]

I think these last couple of commits address this issue, thanks

[sonarqubecloud]

Quality Gate failed

Failed conditions
50.6% Coverage on New Code (required ≥ 80%)
21.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud