Fix secrets checks

[raymondjacobson]

Description

Earlier this week I merged #8167, which made the git secrets tool only installed/updated in postinstall and then with @sddioulde merged #8182, which fixed that functionality.

As it turns out, now that we are properly running the secrets, the aws ones are buggy and yield a lot of false positives.
awslabs/git-secrets#208. Including flagging my recent few prs!

I pulled some secrets to add from here instead https://github.com/h33tlit/secret-regex-list

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.

npm run postinstall
git secrets --scan --cached $(git diff --cached --name-only)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 815d71c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sliptype]

Craziness, thank you for figuring this out!