Start running against "Drupal 12" to help prioritise tooling efforts

Opened 📌 Create TSV that lists Drupal 11 compatible projects Active .

Found 📌 Update to Rector 2.0 Active , that already exists. Added.

Checkmark is misleading actually, remove that. Those issues are not done.

@bbrala points out we have code on our own side to filter project release compatibility, so we don't need d.o changes for this, we can do it ourselves :)

See https://git.drupalcode.org/project/project_analysis/-/blob/master-d11/.g...

Ok we need the following tags in core:

ProjectUpdateBotD12, Drupal 12 compatibility, ProjectUpdateBotD12

I'll make those.

Tags made here 📌 New Drupal 12 compatibility tags Active and updated the default config in the repository to use those.

New branch has been made master-d12, unit test will probably fail.

Project analysis is close to working, having some commit to result branch issues which i need to flesh out. This unfortunately kinda means im not 100 sure how the data is right now. It is available as an artifact of the new master-d12 job.