<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Context We have a super cool push rule to help [prevent users from pushing secrets](https://docs.gitlab.com/ee/push_rules/push_rules.html#prevent-pushing-secrets-to-the-repository) to repositories. ### Proposal We expand the default `files_denylist.yml` file to include more types of files that really shouldn't be pushed to repositories, according to security best practices. #### What to add?? :bulb: We can review open source projects designed to search public repositories for secrets and see what they are looking for and use this to improve our push rule to provide even more value. ([example](https://github.com/eth0izzle/shhgit/blob/master/config.yaml)) <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> Thx to @WarheadsSE for [prompting this](https://gitlab.slack.com/archives/C4Y5DRKLK/p1627055997138600?thread_ts=1627055009.137600&cid=C4Y5DRKLK)