Update the botocore instrumentation to emit events via the logs API instead of the deprecated events API

[DylanRussell]

Description

Move botocore from the deprecated events API to the logs API.

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?

I've updated the existing unit tests to all pass.

Does This PR Require a Core Repo Change?

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

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

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

[DylanRussell]

Updated dependencies to require opentelemetry-api >= 1.35, I think this can be merged now.

[tammy-baylis-swi]

Thanks and nice to see this moving along

[DylanRussell]

ACtually before this goes in I think we need to update the SDK Logger to attach the resource to the LogRecord like the SDK EventLogger does: https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/__init__.py#L654-L764

[tammy-baylis-swi]

ACtually before this goes in I think we need to update the SDK Logger to attach the resource to the LogRecord like the SDK EventLogger does: https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/__init__.py#L654-L764

Trying to follow. Is this related to Logging SDK vs Events SDK emit to init LogRecord with resource?

[DylanRussell]

Yes. Event SDK emit adds resource, logging SDK does not. Logging SDK should do it, and there should be no SDK Log record (that's sort of tangentially related, the SDK logger expects an SDK log record when it should expect an API log record which has no resource on it)

[aabmass]

@DylanRussell is this blocked on releasing open-telemetry/opentelemetry-python#4737?

Please resolve the merge conflict when you have a chance