Increase maxProperties in policies

What does this MR do and why?

This merge request increases the maxProperties values in the JSON schemas for scan execution policies. The changes are made to accommodate additional fields in various scan types without causing validation errors. This update is necessary to support more flexible and feature-rich scan configurations.

Specifically, this MR:

1. Increases maxProperties for DAST scans from 6 to 7.
2. Increases maxProperties for other scan types (SAST, Container Scanning, Dependency Scanning, Secret Detection) from 3-4 to 5.
3. Updates the corresponding test cases to reflect these changes.

These modifications will allow users to include additional configuration options in their scan execution policies without encountering validation errors.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

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

Screenshots or screen recordings

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

Before	After

How to set up and validate locally

1. Check out this branch locally.
2. Run the updated test suite to ensure all tests pass with the new maxProperties values.
3. Create or modify scan execution policies with the maximum number of allowed properties for each scan type to verify that they pass validation.
4. Test edge cases by attempting to add one more property than the new maximum to ensure proper validation errors are thrown.