Very close to #61528
Prerequisite for #61287

At the moment, serialization attributes are read at runtime when framework.serialization.enable_attributes is true.

This means they don't fit for bundles nor can't they be warmed up.

This PR fixes both issues by using a new serializer.attribute_metadata resource tag, that's turned into a list of classes to parse for attributes at compile-time.

For bundles and for apps, the tag is added by explicit service configuration:

        ->set('my_bundle.api_resource.product', Product::class)
            ->resourceTag('serializer.attribute_metadata')

Unlike validation where we have constraint attributes to auto-discover service resources, serialization doesn't have any corresponding hooks. We do have a few like #[DiscriminatorMap] of #[Groups], but relying on those would miss many more classes that are meant for serialization. Maybe we could introduce an attribute that'd hint that some class is serializable by the component (and require the attribute at some point in the future?)