ci: add workflow for cosmos/gosec

[kirbyquerby]

Description

Fixes #10572

This workflow is based on evmos's workflow: https://github.com/evmos/evmos/blob/main/.github/workflows/security.yml

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[kirbyquerby]

/cc @odeke-em @marbar3778

[tac0turtle]

where are the results pushed?

[odeke-em]

where are the results pushed?

@marbar3778 they are reported online in the PR but for the case of ensuring this is merged in before opening the floodgates otherwise the issue would be stapled forever; thus we've disabled reporting until we have breathing space for Q4 2022 but for example please see https://github.com/cosmos/cosmos-sdk/pull/13311/checks?check_run_id=8382756626