[WIP] feat: add http status error configuration

[scott-shields-github]

Description

This PR adds a set of configuration items for custom error flagging based on http status codes. This will allow users of the library to prevent tagging errors for things like a 4xx status code on a server, for example.

This would bring the library closer to the java tracer and some functionalities of the python and c# tracers.

The priority when evaluating spans is:

1. Manually configured error
2. Http status
3. Default - current exception based error tagging

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.38%. Comparing base (aeeec62) to head (f72016d).
Report is 3 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (aeeec62) and HEAD (f72016d). Click for more details.

HEAD has 6 uploads less than BASE

Flag	BASE (aeeec62)	HEAD (f72016d)
tracer-php	12	6

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3223      +/-   ##
============================================
- Coverage     76.38%   67.38%   -9.00%     
+ Complexity     2948      715    -2233     
============================================
  Files           145       68      -77     
  Lines         16076     6148    -9928     
  Branches       1107     1107              
============================================
- Hits          12280     4143    -8137     
+ Misses         3221     1430    -1791     
  Partials        575      575              

Flag	Coverage Δ
appsec-extension	68.80% <ø> (ø)
tracer-php	63.69% <ø> (-15.59%)	⬇️

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

see 87 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 aeeec62...f72016d. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cit-pr-commenter]

PR Security Update

All commits in this PR up to and including 69f19db have been reviewed and marked safe by SDLC security. For any questions, please reach out to #ci-for-external-contributors-collab on Slack.

[bwoebi]

Thanks for the contribution! I've littered the code with suggestions, but it already looks quite good :-)
Tests are obviously broken, but we can regenerate the snapshots.

[scott-shields-github]

Thanks for the contribution! I've littered the code with suggestions, but it already looks quite good :-) Tests are obviously broken, but we can regenerate the snapshots.

Thanks so much for the review and suggestions!

[bwoebi]

Thanks, the code looks fine now - we can have a look at the tests.

[scott-shields-github]

Thanks, the code looks fine now - we can have a look at the tests.

Anything I can do on my end? I've tried to build run the tests in the container, but I've been having trouble with getting it started with docker compose. I've only been able to run the 8.3-buster container and run the tests manually.