<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal It would be nice if DAST can detect rule misconfiguration and return error. This will help the GitLab user who is configuring the DAST job to notice that something went wrong. For instance, [enabling rules](https://gitlab.com/gitlab-org/gitlab/-/blob/07ab57f748b32d71f51052c42b362c66dfb64dfb/.gitlab/ci/dast.gitlab-ci.yml#L101) to like `DAST_ONLY_INCLUDE_RULES: 10010,10011,10017,10029,90033` [won't run](https://gitlab.com/gitlab-org/gitlab/-/jobs/1575052374) any of the these rules as string value is expected which needs to be enclosed in quotes. Here the dast job won't fail which gives the impression that the scan was successful with the enabled rules unless one looks into the logs, which indicates no rules are run (`SUMMARY - PASS: 0 | WARN: 0 | SKIP: 112`) Recently came across similar situation: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69054#note_673367487