When running aws-nuke with a user that lacks the necessary permissions to retrieve details about a specific OpenIDConnectProvider, the tool currently skips all OpenIDConnectProvider resources rather than only the one for which the user lacks permissions. This leads to an incomplete execution of the nuking process.

Expected Behavior:

aws-nuke should log an error when a user lacks permissions to retrieve details about a specific OpenIDConnectProvider, but continue processing the other OpenIDConnectProvider resources, as it would with other resources that have similar permission issues.

Steps to Reproduce:

Run aws-nuke with a user that has insufficient permissions to retrieve information about at least one OpenIDConnectProvider.
Observe that the tool skips all OpenIDConnectProvider resources instead of just the one lacking permissions.
Check the logs for error messages and the halt in processing.

Create a PR to fix this: #576 (wasn't sure if I also had to create an issue)