2.1 & 2.2 BE Catch Server-errors when enabling Secure Features via MR

This Issue tracks the Backend implementation of fixing a Bug when Secret Detection or SAST are enabled via MR through the Security Configuration Page.

How to reproduce: #326532 (comment 1130382230)

Is: The server responds with a status code 500

Should: The server responds with a status code 200 and the following body

{
    "configureSast": {
        "successPath": "",
        "errors": ["$SCANNERNAME merge request creation mutation failed"],
        "__typename": "ConfigureSastPayload"
    }
}