Security Configuration page enablement via MR does not include correct stage

Summary

When enabling security scanners using the Security Configuration page, we fail to include the correct stage in all cases but SAST. This results in an invalid CI configuration file once the MR has been opened

Steps to reproduce

Visit any project's Security Configuration page and attempt to enable a different scanner than SAST (bug is also present with SAST IaC). Once MR is opened check pipeline and see invalid configuration error

What is the current bug behavior?

CI configuration generated is invalid

What is the expected correct behavior?

CI configuration generated should be valid

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com