SAST-rules Add `ci/` Check for Rules without Mapping
Problem to solve
Currently, the ci/
scripts within sast-rules
https://gitlab.com/gitlab-org/security-products/sast-rules do not check whether each rules has a mapping, only whether each mapping has a rule under a valid path.
This has lead to additions of mappings being missed and therefore rules being missed from the sast-rules
and semgrep
releases.
Proposal
Improve the checks in ci/
so this is verified.
cc @craigmsmith