Review and confirm PHPStan suppression specificity improvements

[Copilot]

Reviewed PHPStan configuration changes made in f67e21d that address code review feedback about overly broad error suppressions in PEST test files.

Changes Verified

• HTTP method suppressions: Now explicitly lists Laravel TestCase methods (get|post|put|patch|delete|getJson|postJson|putJson|patchJson|deleteJson) instead of only getJson()
• Assertion suppressions: Changed from wildcard assert.* to explicit list (assertStatus|assertJson|assertJsonStructure|assertJsonFragment|assertJsonPath|assertExactJson|assertSee|assertDontSee)
• Documentation: Added comment explaining PEST framework's PHPStan inference limitations

The suppressions are now appropriately scoped to known Laravel testing methods while maintaining PHPStan level max compliance.

Before (ea92bfe):

- message: '#Call to an undefined method PHPUnit\\Framework\\TestCase::getJson\(\)#'
  path: tests/Feature/*
- message: '#Cannot call method assert.*\(\) on mixed#'  # Too broad
  path: tests/Feature/*

After (f67e21d):

# PEST testing framework limitations: PHPStan cannot infer Laravel TestCase methods
# in PEST's closure-based tests. These are valid Laravel testing methods.
- message: '#Call to an undefined method PHPUnit\\Framework\\TestCase::(get|post|...|deleteJson)\(\)#'
  path: tests/Feature/*
- message: '#Cannot call method (assertStatus|assertJson|...|assertDontSee)\(\) on mixed#'
  path: tests/Feature/*

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}