minor #12005 Remove old versionadded directives (OskarStark)

This PR was merged into the master branch.

Discussion
----------

Remove old versionadded directives

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

c054789 Remove old versionadded directives

Author: OskarStark

bundles.rst

@@ -142,10 +142,6 @@ For example, the **public directory**, which by default is located at
         }
     }
 
-.. versionadded:: 4.4
-
-    The ``getPublicDir()`` method was introduced in Symfony 4.4.
-
 Learn more
 ----------
 

components/browser_kit.rst

@@ -311,10 +311,6 @@ dedicated web crawler or scraper such as `Goutte`_::
         '.table-list-header-toggle a:nth-child(1)'
     )->text());
 
-.. versionadded:: 4.3
-
-    The feature to make external HTTP requests was introduced in Symfony 4.3.
-
 Learn more
 ----------
 

components/http_client.rst

@@ -151,10 +151,6 @@ each request (which overrides any global authentication)::
 
     The NTLM authentication mechanism requires using the cURL transport.
 
-.. versionadded:: 4.4
-
-    The ``auth_ntlm`` option was introduced in Symfony 4.4.
-
 Query String Parameters
 ~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -701,17 +697,9 @@ Now you can make HTTP requests with the PSR-18 client as follows::
 
     $content = json_decode($response->getBody()->getContents(), true);
 
-.. versionadded:: 4.4
-
-    The PSR-17 factory methods of ``Psr18Client`` were introduced in Symfony 4.4.
-
 HTTPlug
 ~~~~~~~
 
-.. versionadded:: 4.4
-
-    Support for HTTPlug was introduced in Symfony 4.4.
-
 The `HTTPlug`_ specification was published before PSR-18 and is superseded by
 it. As such, you should not use it in newly written code. Yet, many libraries
 still require v1 or v2 of it. The component is interoperable with them thanks to

components/lock.rst

@@ -33,11 +33,6 @@ which in turn requires another class to manage the storage of locks::
     $store = new SemaphoreStore();
     $factory = new LockFactory($store);
 
-.. versionadded:: 4.4
-
-    The ``Symfony\Component\Lock\LockFactory`` class was introduced in Symfony
-    4.4. In previous versions it was called ``Symfony\Component\Lock\Factory``.
-
 The lock is created by calling the :method:`Symfony\\Component\\Lock\\LockFactory::createLock`
 method. Its first argument is an arbitrary string that represents the locked
 resource. Then, a call to the :method:`Symfony\\Component\\Lock\\LockInterface::acquire`
@@ -229,12 +224,6 @@ Store                                         Scope   Blocking  Expiring
 :ref:`ZookeeperStore <lock-store-zookeeper>`  remote  no        no
 ============================================  ======  ========  ========
 
-.. versionadded:: 4.4
-
-    The ``PersistStoreInterface`` and ``BlockingStoreInterface`` interfaces were
-    introduced in Symfony 4.4. In previous versions there was only one interface
-    called ``Symfony\Component\Lock\StoreInterface``.
-
 .. _lock-store-flock:
 
 FlockStore

components/messenger.rst

@@ -302,12 +302,6 @@ do is to write your own CSV receiver::
         }
     }
 
-.. versionadded:: 4.3
-
-    In Symfony 4.3, the ``ReceiverInterface`` has changed its methods as shown
-    in the example above. You may need to update your code if you used this
-    interface in previous Symfony versions.
-
 Receiver and Sender on the same Bus
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

components/property_info.rst

@@ -375,11 +375,6 @@ return and scalar types for PHP 7::
     // Initializable information
     $reflectionExtractor->isInitializable($class, $property);
 
-.. versionadded:: 4.1
-
-    The feature to extract the property types from constructor arguments was
-    introduced in Symfony 4.1.
-
 .. note::
 
     When using the Symfony framework, this service is automatically registered

components/var_dumper.rst

@@ -227,10 +227,6 @@ option. Read more about this and other options in
     If you want to use your browser search input, press ``Ctrl. + F`` or
     ``Cmd. + F`` again while having focus on VarDumper's search input.
 
-    .. versionadded:: 4.4
-
-        The feature to use the browser search input was introduced in Symfony 4.4.
-
 Using the VarDumper Component in your PHPUnit Test Suite
 --------------------------------------------------------
 

event_dispatcher.rst

@@ -67,12 +67,6 @@ The most common way to listen to an event is to register an **event listener**::
     Check out the :doc:`Symfony events reference </reference/events>` to see
     what type of object each event provides.
 
-.. versionadded:: 4.3
-
-    The :class:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent` class was
-    introduced in Symfony 4.3. In previous versions it was called
-    ``Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent``.
-
 Now that the class is created, you need to register it as a service and
 notify Symfony that it is a "listener" on the ``kernel.exception`` event by
 using a special "tag":

form/data_transformers.rst

@@ -326,10 +326,6 @@ end-user error message in the data transformer using the
         }
     }
 
-.. versionadded:: 4.3
-
-    The ``setInvalidMessage()`` method was introduced in Symfony 4.3.
-
 That's it! If you're using the
 :ref:`default services.yaml configuration <service-container-services-load-example>`,
 Symfony will automatically know to pass your ``TaskType`` an instance of the

messenger.rst

@@ -895,10 +895,6 @@ stream_max_entries  The maximum number of entries which    ``0`` (which means "n
                     avoid losing pending messages
 ==================  =====================================  =========================
 
-.. versionadded:: 4.4
-
-    The ``stream_max_entries`` option was introduced in Symfony 4.4.
-
 In Memory Transport
 ~~~~~~~~~~~~~~~~~~~