sdk/log: Bring back Processor.Enabled

[pellared]

Problem Statement

The processor's Enabled should also have instrumentation scope and resource as input to e.g. control whether a logger is enabled or not based on logger name.

See: open-telemetry/opentelemetry-specification#4207 (comment)

Proposed Solution

Bring back Enabled to Processor interface and add EnabledParameters type in sdk/log that additionally has Resource and InstrumentationScope getters.

Additional Context

There is a desire in the specification to not stabilize Logger.Enabled API before SDK specifies how it is handled. Therefore, I think we should simply add this functionality and also work on specifying how SDK handles Logger.Enabled.

If I remember correctly, we landed #5692 as we thought that Logger.Enabled would be stabilized in a timely manner which is not happening. I find going back and forth a little annoying. However, I do not see chances to make a v1 of OTel Go Logs in near future, therefore we do not need /x. I also think that exposing this functionality gives us higher chances to receive feedback from users. I also hope that it would also increase the chances to progress with open-telemetry/opentelemetry-specification#4207 as we would support Logger.Enabled in our SDK out-of-the-box.

[pellared]

I want to create a PR for it. I do not want to solve this issue (and merge the PR) before having an agreement from all @open-telemetry/go-maintainers (therefore, probably not sooner than after KubeCon).

[pellared]

Postponing. I first want to create an OTEP. See: open-telemetry/opentelemetry-specification#4207 (comment).

We may decide to go with Filterer, LoggerConfig, or even something different.