[CodingStyle] Drop AnnotateThrowablesRector to narrow code scope, designed for custom community rule

[TomasVotruba]

Hi @Aerendir ,

as this PR is related to your contribution, #2998, we though we should let you know about it.

We're trying to deliver Rector to the wider community, with lower PHP as PHP 5.6 and prefixed dependencies.
Current Rector code-base is now bloated with rule, that should have been implemented by community itself. This drags development itself down, we don't have coding power to maintain all this while developing new features and keeping up to date with legacy code requirements.

To this burden gropus belonged 3 Phalcon rules (#5313), Sonarcube (#5215) or events (#4865).

Saying that, we're dropping few rules, to be able to improve code base. We pick rules that can be adapated by community, like this. We'd be happy if this code is moved, maintained and used in external package as the idea itself is valid 👍

For inspiration, sSimilar community work is done in:

• Drupal: https://github.com/palantirnet/drupal-rector
• Typo3: https://github.com/sabbelasichon/typo3-rector

We know it's not a convenient, but we hope you take it well for Rector be able to grow 🙂

Let us know if you need any help with migration. We'll be happy to help 👍

[Aerendir]

Hi @TomasVotruba , thank you for the message :)

I'm not currently using the rule anymore.

It had a lot of improvements to be done, and caused a lot of issues as it requires multiple runs to annotate properly the methods.

In this moment I think that, also if the idea is good, the implementation effort is really too much compared to the benefit :(

[TomasVotruba]

Thank you for reaching out and for the feedback 👍