[componentattribute] Use otelzap.WithAttributes, remove LoggerProviderWithAttributes (#13108)

#### Description

Now that `otelzap` has been bumped up to 0.11.0 (#13103), this PR
follows up on a TODO comment to use
open-telemetry/opentelemetry-go-contrib#6962 to
set instrumentation scope attributes on the Logger created by otelzap,
instead of a workaround (`LoggerProviderWithAttributes`).

This is an internal change, and the new code should be functionally
equivalent, so I don't think this needs a changelog.

#### Testing

I believe this is already covered by existing tests.

Author: jade-guiton-dd

internal/telemetry/componentattribute/logger_provider.go

@@ -86,12 +86,10 @@ var _ coreWithAttributes = (*otelTeeCoreWithAttributes)(nil)
 //
 // This is used when service::telemetry::logs::processors is configured.
 func NewOTelTeeCoreWithAttributes(consoleCore zapcore.Core, lp log.LoggerProvider, scopeName string, level zapcore.Level, attrs attribute.Set, wrapper func(zapcore.Core) zapcore.Core) zapcore.Core {
-	// TODO: Use `otelzap.WithAttributes` and remove `LoggerProviderWithAttributes`
-	// once we've upgraded to otelzap v0.11.0.
-	lpwa := LoggerProviderWithAttributes(lp, attrs)
 	otelCore, err := zapcore.NewIncreaseLevelCore(otelzap.NewCore(
 		scopeName,
-		otelzap.WithLoggerProvider(lpwa),
+		otelzap.WithLoggerProvider(lp),
+		otelzap.WithAttributes(attrs.ToSlice()...),
 	), zap.NewAtomicLevelAt(level))
 	if err != nil {
 		panic(err)