fix(with-incident-details): Ensure the token has the correct scope

[salome-voltz]

Context

ggshield 1.32.0 can now return the details of an incident when a scan is run with the --with-incident-details option. For this feature to work, the token used to authenticate with the API must have the 'incidents:read' scope. This is currently not documented and if the token does not have the required scope, the flag will be silently ignored.

What has been done

Ensure the token has the required scope before running a command with --with-incident-details flag. This MR goes with GitGuardian/py-gitguardian#126

PR check list

• As much as possible, the changes include tests (unit and/or functional)
• If the changes affect the end user (new feature, behavior change, bug fix) then the PR has a changelog entry (see doc/dev/getting-started.md). If the changes do not affect the end user, then the skip-changelog label has been added to the PR.

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.

Project coverage is 92.04%. Comparing base (b82d7ca) to head (6462217).

Files with missing lines	Patch %	Lines
ggshield/verticals/secret/secret_scanner.py	90.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1015   +/-   ##
=======================================
  Coverage   92.04%   92.04%           
=======================================
  Files         181      181           
  Lines        7704     7717   +13     
=======================================
+ Hits         7091     7103   +12     
- Misses        613      614    +1     

Flag	Coverage Δ
unittests	92.04% <94.11%> (+<0.01%)	⬆️

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

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[sevbch]

Seems alright with me! 🙂 (though it's my very first review here)

(Don't forget to revert pdm update once GitGuardian/py-gitguardian#126 is released)