Add pre scan verification step create-update service

What does this MR do and why?

We are creating a pre-scan verification for DAST scans as described in issue #366456.

The pre-scan will check if:

1. We can connect to the target site.
2. If authentication is specified, we can authenticate to the target site.
3. We are able to follow links and crawl up to 3 pages without errors.

After each check, the analyzer will send the results to an internal API. We will be saved on the table dast_pre_scans_verification_steps.

This MR adds a new service to create/update the records in the dast_pre_scans_verification_steps table.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.