When configuring services like normalizers for a named serializer or Monolog processors for specific channels/handlers, autoconfiguration can get in the way.

For example, the NormalizerInterface is registered for autoconfiguration.
If I try to register a custom normalizer for a specific named serializer, it also gets registered with the default serializer because of autoconfiguration:

#[AutoconfigureTag(
    name: 'serializer.normalizer',
    attributes: [
        'serializer' => 'my_named_serializer',
    ],
)]
class MyNormalizer implements NormalizerInterface {}

Currently, the only way around this is to disable autoconfiguration entirely:

services:
    App\MyNormalizer:
        autoconfigure: false
        tags:
            - serializer.normalizer: { serializer: 'my_named_serializer' }

This PR introduces a new inherit_configuration option for service definitions and a #[WithoutInheritedConfiguration] attribute.
Both allow skipping the inheritance of instanceof conditionals from parent classes or interfaces:

#[AutoconfigureTag(
    name: 'serializer.normalizer',
    attributes: [
        'serializer' => 'my_named_serializer',
    ],
)]
#[WithoutInheritedConfiguration]
class MyNormalizer implements NormalizerInterface {}

It can also be used to exclude specific services from inheriting _instanceof configurations:

services:
    _defaults:
        autowire: true
        autoconfigure: true

    _instanceof:
        App\SomeInterface:
            tags: ['some.tag']

    App\SomeInterfaceImplementation:
        inherit_configuration: false # This implementation won't inherit instanceof config

Why a new attribute?

I initially tried adding a new argument to the existing #[Autoconfigure] attribute.
However, this attribute itself is resolved via instanceof conditionals.
I could try something like $conditionals[$class], but since the attribute is repeatable, it’s unclear how to handle cases like:

#[Autoconfigure(inheritConfiguration: false)]
#[Autoconfigure(inheritConfiguration: true)]
class MyClass {}