Remove doctrine annotations

[mgiraud]

Closes #181
Closes #176

At first it thought about keeping the annotation classes, but they become useless.
Edit : Keep them anyway to avoid potential BC Break

[bocharsky-bw]

I have no experience with phpstan/phpdoc-parser, but I see test sare happy with this change, so it looks good to me.

Could you also fix failed SA?

[bocharsky-bw]

Hm, I'm thinking about doing a minor release for this... but if we completely drop annotation files like ‎src/Annotation/Desc.php - it will be still a BC break, right? I wonder if we should revert removing them and keep them deprecated for a while in this project, along with the doctrine/annotations package? I suppose if users will not stop using them in their projects - there should not be deprecation warnings for them, right? WDYT?

[mgiraud]

I guess you are right. Some users might use them in an other way than annotations.
Will revert the removal tomorrow (or you can do it if you want). Do you have a preference on how to deprecate theses classes ?

[mgiraud]

I've have added a @deprecated tag on each annotation class.
I've considered adding trigger_error(..., E_USER_DEPRECATED); in the construct of each class but that seems overkill

[bocharsky-bw]

I'm fine for now with @deprecated for now, though I think if we really want to push users to get rid of it in their projects, we may need to trigger_deprecation() also, see https://symfony.com/doc/current/contributing/code/conventions.html#deprecating-code . Because simple @deprecated won't be enough to trigger a deprecation notice for users. But I think we can do it in another PR too

[mgiraud]

trigger_deprecation is great, but we need to pull another crate symfony/deprecation-contracts.
Certainly worth as there are already multiple symfony crates required by this lib.
Will do in an other PR.

[bocharsky-bw]

Thank you for working on this! Let's merge