Make Laravel appsec login success event more accurate

[estringana]

Description

It has been reported that the previous approach to trigger successful logins is not accurate. This results on some endpoints reporting successful login events on every request instead of just when a user gets logged in into the system. This PR attach the event to the event provided by Laravel

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[codecov-commenter]

Codecov Report

Merging #2600 (fc98f13) into master (3d4313f) will decrease coverage by 12.14%.
The diff coverage is 0.00%.

Additional details and impacted files

@@              Coverage Diff              @@
##             master    #2600       +/-   ##
=============================================
- Coverage     76.90%   64.76%   -12.14%     
  Complexity     2564     2564               
=============================================
  Files           215      215               
  Lines         23095    23095               
=============================================
- Hits          17761    14958     -2803     
- Misses         5334     8137     +2803     

Flag	Coverage Δ
tracer-extension	78.66% <ø> (+<0.01%)	⬆️
tracer-php	47.50% <0.00%> (-27.23%)	⬇️

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

Files	Coverage Δ
...ations/Integrations/Laravel/LaravelIntegration.php	0.00% <0.00%> (-81.91%)	⬇️

... and 19 files with indirect coverage changes

---

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 3d4313f...fc98f13. Read the comment docs.

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-03-28 09:41:16

Comparing candidate commit fc98f13 in PR branch estringana/improve-login-success-laravel-event with baseline commit 3d4313f in branch master.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 181 metrics, 0 unstable metrics.

scenario:TraceSerializationBench/benchSerializeTrace

• 🟩 execution_time [-13.487µs; -10.413µs] or [-7.245%; -5.594%]

[Anilm3]

lgtm

[PROFeNoM]

LGTM! 🛥️