Update LogRecord API to set and make use of context to set trace id / span id / trace flags,

[DylanRussell]

Description

Basically just a continuation of #4597. My PR just updates the API LogRecord to match what the SDK LogRecord does with context..

This will help me migrate instrumentations using the API Event to use the API LogRecord,.. I ran into an issue migrating one of the instrumentations that relies on EventsLogger.emit getting the context and using it to set trace/spanid: https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/_events/__init__.py#L52

There is no equivalent logic in the Logger, but this PR adds it..

Type of change

Please delete options that are not relevant.

• [x ] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Unit tests

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR:
• [x ] No.

Checklist:

• [ x] Followed the style guidelines of this project
• Changelogs have been updated
• [ x] Unit tests have been added
• [ x] Documentation has been updated

[DylanRussell]

@emdneto @tammy-baylis-swi can I get your thoughts/reviews on this PR ?

[tammy-baylis-swi]

I think this is good. It's safer than changing the LogRecord init by the Event API immediately to pass context instead of trace_id etc, plus wherever else.