[HttpKernel] Deprecate all occurrences of ArgumentValueResolverInterface

components/http_kernel.rst

@@ -340,12 +340,19 @@ of arguments that should be passed when executing that callable.
        available through the `variadic`_ argument.
 
     This functionality is provided by resolvers implementing the
-    :class:`Symfony\\Component\\HttpKernel\\Controller\\ArgumentValueResolverInterface`.
+    :class:`Symfony\\Component\\HttpKernel\\Controller\\ValueResolverInterface`.
     There are four implementations which provide the default behavior of
     Symfony but customization is the key here. By implementing the
-    ``ArgumentValueResolverInterface`` yourself and passing this to the
+    ``ValueResolverInterface`` yourself and passing this to the
     ``ArgumentResolver``, you can extend this functionality.
 
+    .. versionadded:: 6.2
+
+        The ``ValueResolverInterface`` was introduced in Symfony 6.2. Prior to
+        6.2, you had to use the
+        :class:`Symfony\\Component\\HttpKernel\\Controller\\ArgumentValueResolverInterface`,
+        which defines different methods.
+
 .. _component-http-kernel-calling-controller:
 
 5) Calling the Controller

reference/dic_tags.rst

@@ -333,10 +333,17 @@ controller.argument_value_resolver
 **Purpose**: Register a value resolver for controller arguments such as ``Request``
 
 Value resolvers implement the
-:class:`Symfony\\Component\\HttpKernel\\Controller\\ArgumentValueResolverInterface`
+:class:`Symfony\\Component\\HttpKernel\\Controller\\ValueResolverInterface`
 and are used to resolve argument values for controllers as described here:
 :doc:`/controller/argument_value_resolver`.
 
+.. versionadded:: 6.2
+
+    The ``ValueResolverInterface`` was introduced in Symfony 6.2. Prior to
+    6.2, you had to use the
+    :class:`Symfony\\Component\\HttpKernel\\Controller\\ArgumentValueResolverInterface`,
+    which defines different methods.
+
 data_collector
 --------------