Hardcode eslint and Gosec ids and primary ids in to mapping
What does this MR do?
Hardcode all the IDs and Primary Identifiers into the eslint and gosec mapping files.
This change should have no effect on the generated rules, as all the IDs and primary IDs are the same as those already in the ruleset.
The purpose of this change is to ensure primary identifiers and IDs are predictable and to reduce complexity from the deploy script
What are the related issue numbers?
Edited by Craig Smith