Add Azure Resource Logs translator

[MikeGoldsmith]

Description:

This PR adds a new Azure Resource Logs translator that can be used to convert Azure events into resource logs events using Semantic conventions defined here here.

This supersedes following draft PR by updating it to have the latest semconv:

• Azure Event Hub receiver Semantic Convention translator #32486

Note: A follow-up PR will update the Azure receiver to use the new translator.

Testing:

Includes unit tests to verify expected behaviours and data structures.

Documentation:

---

cc @markrendle @lmolkova @TylerHelmuth

[MikeGoldsmith]

I'm a little unsure why both the changelog is failing:

and why the receiver is failing with a missing go.sum entry

Any help would be appreciated 😄

[cparkins]

@MikeGoldsmith I would remove the '[user]' from your change log entry and see if it fixes the issue since it says it's the default value anyway. I'll also look into the go mod issue, although I always struggle with those too!

[atoulme]

single quotes around your array makes it a string '[user]'

[cparkins]

@MikeGoldsmith I submitted a PR to your fork to try and address some of the build issues.

[MikeGoldsmith]

Thank you @cparkins, I'll take a look shortly.

[an-mmx]

Hey @MikeGoldsmith ,

Sorry for the late reply. It seems i've missed some updates.
I've seen your changes for properties type check and this probably a good solution. The properties of FunctionAppLogs is now stored as string attribute.

I believe it would be a good in next step to introduce the possibility to enable corrections to JSON string so that it would be possible to apply semantic conventions translation. We do it unconditionally in our implementation (you can check it in this commit). I agree, It's not the best approach. It worth to add some extra logic to make it optional and keep the properties in attributes when failed to parse JSON. Nevertheless it allows us to apply translations. I'd like to hear your thoughts on this.

There is also another commit with the time convertion approach. I would like to create a PR with these changes for the both azure and azurelogs translators, after #35357 is being merged. Of curse, if no objections?