### Description:
This PR addresses an issue where a buggy verification process was incorrectly marking false-positive credentials as verified. The following cases are now handled properly:
- Malformed `authorization_code` Request:
If an invalid authorization_code request is sent for verification, the API responds with a 403 Forbidden status and an invalid_grant error code.
Fix: These credentials will now be marked as verified in this case.
- Unauthorized Client:
If the credentials do not have permission to make an authorization_code request, the API returns a 403 Forbidden status with the unauthorized_client error code.
Fix: No change in behavior; this case continues to be handled correctly.
- Invalid Domain:
If the provided domain is not valid, the API returns a 404 Not Found status.
Fix: These credentials will now be correctly marked as unverified.
- Invalid ID/Secret:
If the client ID or secret is invalid, the API responds with a 401 Unauthorized status.
Fix: These credentials will now be correctly marked as unverified.
This PR ensures a more accurate verification process and reduces false positives.
Here is the results of modified test results:
### Checklist:
* [ ] Tests passing (`make test-community`)?
* [x] Lint passing (`make lint` this requires [golangci-lint](https://golangci-lint.run/welcome/install/#local-installation))?
Abdul Basit
985eb75a46