Use custom resolver for extracting type information from docblocks

[micheleorselli]

This is a possibile approach to solve #497: the code needed to parse docblock types is now in a class indipendent from PhpParser's NameResolver. This would give us more flexibility and mantainability .

Further evolution could be (to be tackled in subsequent PRs)

• extracting information for @throws tags and consider them as dependencies
• simplify the way we get information on types from the docblocks

[codecov]

Codecov Report

Attention: Patch coverage is 91.40625% with 11 lines in your changes missing coverage. Please review.

Project coverage is 97.31%. Comparing base (96cd45c) to head (af8fe00).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/Analyzer/DocblockTypesResolver.php	93.26%	7 Missing ⚠️
src/Analyzer/DocblockParserFactory.php	71.42%	4 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #504      +/-   ##
============================================
+ Coverage     95.92%   97.31%   +1.38%     
+ Complexity      671      624      -47     
============================================
  Files            76       78       +2     
  Lines          1839     1748      -91     
============================================
- Hits           1764     1701      -63     
+ Misses           75       47      -28     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.4% Duplication on New Code

See analysis details on SonarQube Cloud

[AlessandroMinoccheri]

Despite the error in the pipeline, for me it's fine.

LGTM 👍