Implement merging of Resources with different schemas in resourcedetectionprocessor

[tigrannajaryan]

resourcedetectionprocessor modifies the Resources that pass through it by merging it with the Resources
it detected. This merging is valid when the schemas of the original Resource and the merged Resource
are the same, but it is generally speaking incorrect when the schemas are different.

Proposed OTEP 0161 defines how Resources of different schemas can be merged correctly by leveraging
schema conversion capabilities:
https://github.com/open-telemetry/oteps/blob/b2cb1558c6fa88535ef68f7a19df147a1b6fc162/text/0161-telemetry-schema-and-resource.md#resource-merge-logic

Once we have a code that implements schema conversion we can use it in resourcedetectionprocessor's
MergeSchemaURL/MergeResource functions.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[tigrannajaryan]

Depends on #5036

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[tigrannajaryan]

This is waiting for OTEP 0161 and for schema processor implementation.

[github-actions]

Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.