[meta] Convert all core plugin types to attribute discovery

Meta question, is this enough of a meta issue to encompass the entirety of moving from annotations to attributes, or should we also open a parent 'plan' issue that encompasses this and any other attribute issues that come up (like deprecations and so on)?

I think we should start by opening child issues here to finish off actions (only needs deprecations now?) and blocks (two remaining blocks plus deprecations?) and then go from there.

Added #3265945: Triggering deprecations for plugins using annotations when core plugin type has been converted to attributes as a child as it seems the best place for it right now.

@berdir @longwave just opened a new issue to discuss that #3400121: [policy, no patch] Allow both annotations and attributes in Drupal 11

Added child issues for all plugin types except \Drupal\plugin_test_extended\Plugin\Annotation\PluginExtended which we can sort out later.

Updated issue summary with list

Unless I am mistaken, there is also the views handler, \Drupal\views\Plugin\ViewsHandlerManager.

Updated IS with link to https://github.com/palantirnet/drupal-rector/pull/257

@bbrala polished 10.2 conversions already

@quietone yes, views plugins are the last and could use own META

Added #3425568: Block attribute class expecting wrong ContextDefinition which may also impact other plugins too

Added #3426217: Fix @param docs for $deriver on plugin attribute classes

This is releasing very soon:

https://github.com/palantirnet/drupal-rector/blob/2cc2787bd323406b7da4f4...

Tracked in this PR: https://github.com/palantirnet/drupal-rector/pull/296

Tested on this issue: https://www.drupal.org/project/drupal/issues/3396166 (see the MR for the automated branch)

Released here:

https://github.com/palantirnet/drupal-rector/releases/tag/0.20.1

Includes usage docs for Core conversions. Hopefully it helps speed things up.

Added 7 more views plugin types for conversion

Fun fact, you can run the rector on an existing MR to check if something was missed. It will skip over any classes already implementing the attribute.

Sorted the task list a bit

Added #3427388: Update Drupal\Component\Annotation\Doctrine\StaticReflectionParser::hasClassAttribute() to allow attribute subclasses to the list to handle subclasses.

Issue summary updates: Remove Tip from the issue summary because it will be done in contrib. And added #3265945: Triggering deprecations for plugins using annotations when core plugin type has been converted to attributes.

Earlier this week I did a check using a branch with all converted plugins in rector against head. Source of the list was the change record.

https://github.com/palantirnet/drupal-rector/tree/feature/annotation-rules

Good news, there were no conversions missing.

@Berdir sent me a message there were a few missing.

Examples:

PreviewAwareBlock
AnnounceBlock

So i've looked into why this is. Might be me doing not smart things while scripting.

Ok, i've done a booboo when making the script. Aftersome tweaks:

AnnounceBlock.php
InlineBlock.php
PreviewAwareBlock.php
TestXSSTitleBlock.php

The BooBoo were a few things:

My config added classes instead of the annotations. Rector didnt like backslashes before the classes, so did some extra normization actions. I'll push how i ran on core to a branch here.

Compare changes on GitLab

@bbrala great job! Looks only formatting left to apply and it could be reused for contrib!

Added #3258581: Move I18nQueryTrait from content_translation to migrate_drupal to the remaining tasks for visibility, because it's a blocker for #3421014: [PP-1] Convert MigrateSource plugin discovery to attributes.

Tagging this so it's easier to find in 'things that would be good to do for 11.0/10.3 beta'.

This may be the wrong place for this (apologies if so).

The change record and documentation state Drupal 10.2.0 plugins should start using attribute-based instead of annotation-based plugins, but the core plugins don't actually support attribute-based discovery until 10.3.x. Can there be more clear documentation stating it's not well-supported yet until 10.3.x?

Relevant links:
- https://www.drupal.org/node/3403921 (10.2)
- https://www.drupal.org/node/3395575 (10.2)
- https://www.drupal.org/node/3229001 (10.3)