DAST site validation gets stuck forever

What does this MR do and why?

Describe in detail what your merge request does and why.

This MR resolves #369938

This is first iteration of fixing the problem with stuck validation.

New method is introduced getValidationStatus.

It checks explicitly if validation is running over an hour, and if it does, validation status would be changed to failed. Check relies on newly introduced validationStartedAt field.

Screenshots or screen recordings

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

UI	Screenshot
List of site profiles

How to set up and validate locally

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

1. In order to test locally, you need to have validate.sh file on your machine validate.sh
2. Go to /-/security/configuration/profile_library#site-profiles on project level
3. Create site profile if there is none
4. Return to site profile list and click validate
5. Most likely validation won't stuck
6. In order to test it, you can follow this instruction

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.

Related to #369938