Fix Sentry logging details

[briskt]

IDP-779 Sentry log events are sometimes "unlabeled"

---

Added

• Added the idp name to Sentry issues as a tag. This is searchable, sortable, and more visible than a context entry.

Fixed

• Log a useful message to Sentry in cases where no explicit "message" key is included
• Fixed one specific error instance that had neither "message" nor "error"

Changed

• Don't report user-generated error messages (i.e. http status codes 400, 401, 404, and 409)

---

PR Checklist

• Documentation (README, local.env.dist, api.raml, etc.)
• Tests created or updated
• Run make composershow
• Run make psr2

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[hobbitronics]

Looks good, but I don't understand the dependencies.json file.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud