Add methods to find DAST profiles with given name

What does this MR do?

This change adds new scopes, methods and extends finders with ability to search for DAST scanner and site profiles with provided names.

This MR was extracted from WIP MR with all needed changes: !54067 (closed)

Queries

SELECT “dast_scanner_profiles”.* FROM “dast_scanner_profiles” WHERE “dast_scanner_profiles”.“project_id” = 23464116 AND “dast_scanner_profiles”.“name” = ‘Scanner A’;

https://explain.depesz.com/s/ujql (~1.9ms)

SELECT “dast_site_profiles”.* FROM “dast_site_profiles” WHERE “dast_site_profiles”.“project_id” = 23464116 AND “dast_site_profiles”.“name” = ‘Site A’;

https://explain.depesz.com/s/CGX (~1.6ms)

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry

Not needed:

Any developer-facing change (e.g., refactoring, technical debt remediation, test suite changes) should not have a changelog entry. Example: “Reduce database records created during Cycle Analytics model spec.”

• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team

Related to #299215 (closed)