Add `Event Enabled` operation to `Logger`

[pellared]

Do we need a separate operation like Event Enabled to help users avoiding performing computationally expensive operations when generating events? Or can we reuse the existing Logger.Enabled?

Related to:

• SeverityNumber as required parameter in EmitEvent #4261
• Add EventName parameter to Logger.Enabled #4220

Experimental implementations:

• C++: https://github.com/open-telemetry/opentelemetry-cpp/blob/f69963f587b148d2eb20f7d30f8b4a1ccb184a6f/api/include/opentelemetry/logs/logger.h#L251-L276
• Rust: https://github.com/open-telemetry/opentelemetry-rust/blob/8d84a76b8f8aaa0d625ab67a16320680c276f6b5/opentelemetry/src/logs/logger.rs#L23-L25

Parameters:

• context (optional/required - depending on the language)
• event name (required)
• severity level (required)

Originally posted by @pellared in #4259 (comment)

[pellared]

Closing per:

• logs: Remove Events operations in favor of making whole Logger user-facing #4352