[sdk-logs] Update LogRecord to keep CategoryName and Logger in sync

[CodeBlanch]

Follow-up to #5300 (comment)

Changes

• Updated ILogger path to set LogRecord.Logger to a Logger built from CategoryName.
• Updated LogRecord.CategoryName getter to return LogRecord.Logger.Name.
• Updated LogRecord.CategoryName setter to change LogRecord.Logger (if needed).
• Updated OtlpLogExporter to only look at LogRecord.Logger.Name.

Details

The big benefit to this change is if users start using something which is emitting logs via the Log Bridge API AND they use an exporter coded to expect CategoryName they will now have something set.

One thing @alanwest will like is OtlpLogExporter no longer has any knowledge of CategoryName. You're welcome @alanwest! 😄

Merge requirement checklist

• CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
• Unit tests added/updated
• Appropriate CHANGELOG.md files updated for non-trivial changes

[alanwest]

One thing @alanwest will like is OtlpLogExporter no longer has any knowledge of CategoryName.

Yes I do like it. But c'mon don't we all like a little spec compliance?

[rajkumar-rangaraj]

In the tests, we are proving that the values of logRecord.Logger.Name and logRecord.CategoryName are the same. Is there any difference in using one over the other in this context?

[cijothomas]

OTLPExporter can remain agnostic to ILogger specific CategoryName.

[CodeBlanch]

No practical difference between the two. This is more of a philosophical change which brings OtlpExporter closer to the spec. The goal being it doesn't know anything about any specific logging framework (ILogger being one of those).