[configuration] Add example using hexadecimal notation

[mx-psi]

Updates #3959

Changes

Adds example for using an integer in hexadecimal notation. The intention is to show the difference when quoting vs not quoting and make explicit that quoting means keeping the original representation (we already have the true example but this one has two different representations).

I think this is already implied by the text so this is only a change in the example.

• Related issues Add example of env expansion with non-standard integer notation #3959, part of Alignment with OpenTelemetry Collector configuration #3963

[mx-psi]

cc @open-telemetry/configuration-maintainers

[mx-psi]

Also cc @evan-bradley @astencel-sumo @swiatekm-sumo since we discussed something related at Kubecon, in case you want to take a look :)

[mx-psi]

Since the behavior here depends on supporting the core schema I am going to mark this as draft until we decide on #3973

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.

[mx-psi]

Will ask for this to be reopened once we resolve #3973

[mx-psi]

@jack-berg would you be able to reopen this? I don't have permissions and want to retake this after #3973 has been merged

[mx-psi]

This just exemplifies what should happen now that we have #3973: 0xdeadbeef SHOULD be parsed as a number if unquoted, and as a string if quoted (given that environment variable resolution happens before YAML parsing)

[jack-berg]

Seems good to me. I updated the java implementation to reflect this: open-telemetry/opentelemetry-java#6436