[TASK] Remove deprecation information for list-type (#5971)

* [TASK] Remove deprecation information for list-type

Releases: main

* Update Documentation/ExtensionArchitecture/BestPractises/NamingConventions.rst

* Update Documentation/ExtensionArchitecture/BestPractises/NamingConventions.rst

* Update Documentation/ExtensionArchitecture/BestPractises/NamingConventions.rst

* Update Documentation/ExtensionArchitecture/BestPractises/NamingConventions.rst

* [TASK] Fix link

Author: linawolf

Documentation/ApiOverview/ContentElements/Index.rst

@@ -19,7 +19,6 @@ created, how existing content elements or plugins can be customized etc.
     CustomBackendPreview
     ContentElementsWizard
     BestPractices
-    MigrationListType
 
 ..  _cePluginsIntroduction:
 
@@ -144,10 +143,6 @@ An Extbase plugin is configured for the frontend with
 ..  literalinclude:: _Plugins/_ext_localconf_extbase_plugin.php
     :caption: EXT:my_extension/ext_localconf.php
 
-..  deprecated:: 13.4
-    Setting the fifth parameter to any value but `ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT`
-    is deprecated. See :ref:`plugins-list_type-migration`.
-
 Method :php:`ExtensionUtility::configurePlugin()` also takes care of registering
 the plugin for frontend output in TypoScript using an object of type
 :ref:`EXTBASEPLUGIN <t3tsref:cobj-extbaseplugin>`.

Documentation/ApiOverview/ContentElements/MigrationListType.rst

@@ -342,7 +342,7 @@ Plugin signature
 ..  versionchanged:: 14.0
     Adding frontend plugins as a "General Plugin", setting the content
     record :sql:`CType` to :sql:`'list'` and `list_type` to the plugin signature
-    is not possible anymore. See :ref:`plugins-list_type-migration`.
+    is not possible anymore. See `Migration <https://docs.typo3.org/permalink/t3coreapi:plugins-list_type-migration@13.4>`__.
 
 The plugin signature of non-Extbase plugins, registered via
 :php:`ExtensionManagementUtility::addPlugin()` is an arbitrarily defined string.

Documentation/ApiOverview/ContentElements/_Migration/PluginListTypeToCTypeUpdate.php

@@ -47,12 +47,7 @@ Use the following steps to add the plugin as content element:
     #.  A unique identifier for your plugin in UpperCamelCase: :php:`'PostSingle'`
     #.  An array of allowed combinations of controllers and actions stored in an array
     #.  (Optional) an array of controller name and  action names which should not be cached
-    #.  Using any value but `ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT` is
-        deprecated in TYPO3 v13.4.
-
-    ..  deprecated:: 13.4
-        Setting the fifth parameter to any value but `ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT`
-        is deprecated. See :ref:`plugins-list_type-migration`.
+    #.  `ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT`
 
     :php:`TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin()` generates
     the necessary TypoScript to display the plugin in the frontend.

Documentation/ApiOverview/ContentElements/_Migration/_ext_localconf.php.diff

@@ -8,10 +8,6 @@
 Frontend plugin
 ===============
 
-..  deprecated:: 13.4
-    Adding frontend plugins as a "General Plugin", setting the content
-    record :sql:`CType` to :sql:`'list'` is deprecated. See :ref:`plugins-list_type-migration`.
-
 The term "frontend plugin" describes a part of a TYPO3 extension that is
 handled like a content element (can be inserted like a record/element in
 the TYPO3 backend by editors), which will deliver dynamic output when