Fix enum-typed scan profile configuration values on the GraphQL wire

What does this MR do and why?

imageSuffix and advancedSastPartialScan were sent and read using the backend CI-variable value (e.g. -fips) instead of the GraphQL enum name (FIPS) required on the wire, so saving a scan profile with either field set failed with a variable coercion error. This translates values at the mapScanProfileVariables/readScanProfileTriggers boundary so the rest of the frontend keeps reasoning in terms of the backend-facing value.

References

• issue: [Frontend] Scan profile drawer: view, create, e... (#624191 - closed)

Screenshots or screen recordings

No UI change, this is a GraphQL wire-encoding fix.

How to set up and validate locally

1. Open Manage profiles for a SAST scan profile in the security configuration.
2. Set the Image suffix (or Advanced SAST partial scan) advanced configuration value for a trigger.
3. Save. Before this fix, saving errors with a variable coercion error; after, it saves and the value round-trips correctly on reload.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.