[TASK] Deprecate plugin content element and plugin subtypes (list_type)

Historically, plugins were commonly registered as subtypes of the
content element `list` by using the `list_type` field. In this setup,
`CType` was set to `list` for all plugins, while the actual plugin
key was defined in the `list_type` field.

This approach however led to several problems:

* Different plugins required different fields in the backend form,
  resulting in complex and often convoluted TCA configurations to
  manage form behavior.
* The existence of the `list_type` made a separate layer of content
  element definitions in the TypoScript necessary.
* The use of `list_type` did not provide any significant benefits
  and made permission handling and other backend processes more
  cumbersome.

The recommended way to create plugins is to use dedicated `CType`
content elements for each plugin. Several popular TER extensions
have already migrated from `list_type` to `CType` plugins.

In order to unify content element registration and to remove
various `list_type` related core hacks, the plugin content element
and plugin subtypes have therefore been deprecated.

The deprecation introduces the new `AbstractListTypeToCTypeUpdate`
update wizard, which 3rd party extension authors can extend in
order to add a update wizard to custom extension, which performs
the required record and backend user permission migration.

To prevent hundreds of functional tests showing a deprecation
warning, several fixture extensions have been adapted, so
plugins are configured as `CType`.

Resolves: #105076
Releases: main
Change-Id: I82532377cf5764ad90b55aa0ff3e16b4bea74a3d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86253


Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Oliver Bartsch <bo@cedev.de>