Record spans for symfony messenger

[cedricziel]

This instrumentation adds spans for the Symfony messenger component.

It creates:

• an internal span when a message is sent to a MessageBusInterface
• an internal span, when a message is sent to a transport

Nota bene:

• enable all testsuites in PHP unit
• configure Github Actions to only run one job in parallel per PR and cancel existing run when new commits are pushed

[codecov]

Codecov Report

Merging #215 (48eb722) into main (de8340c) will increase coverage by 0.09%.
The diff coverage is 89.00%.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #215      +/-   ##
============================================
+ Coverage     85.85%   85.94%   +0.09%     
- Complexity      883      888       +5     
============================================
  Files            80       81       +1     
  Lines          3393     3493     +100     
============================================
+ Hits           2913     3002      +89     
- Misses          480      491      +11     

Flag	Coverage Δ
7.4	85.63% <ø> (ø)
8.0	85.34% <89.00%> (+0.11%)	⬆️
8.1	85.38% <89.00%> (+0.11%)	⬆️
8.2	85.88% <89.00%> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...mentation/Symfony/src/MessengerInstrumentation.php	89.00% <89.00%> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update de8340c...48eb722. Read the comment docs.

[cedricziel]

PSR-3 testsuite is broken..

[brettmc]

@cedricziel you can leave the psr3 failures to me, those tests haven't been running previously.

[brettmc]

The psr-3 failures are sort of xdebug-related. I was able to replicate this locally, and it occurs when running the .phpt tests with coverage enabled, whilst actually generating coverage. eg XDEBUG_MODE=coverage vendor/bin/phpunit --coverage-text
With this command, the output from the phpt test is different (it looks like exporting did not happen, or at least did not make it to console).

So, #217 is a compromise: we run all tests without generating coverage (which includes any phpt tests), and generate coverage only off the unit & integration suites.

The reason this failed to fail previously is that --testsuite unit --testsuite integration is not the right way to run two suites, one clobbers the other. You need to --testsuite unit,integration.

[brettmc]

@cedricziel merging in main should make the build green.

[cedricziel]

Done @brettmc ! Thanks for the thorough review! 🙏