Update DAST Profiles links to use the new route

Related #324583 (closed)

This is the second part to DAST security configuration route update, and should be merged after !56960 (merged) deployment to adhere to multi version compatibility guidelines

What does this MR do?

This MR updates all links to use dast_scans route instead of dast_profiles.

dast_scans => dast_profiles

Screenshots (strongly suggested)

No visual changes

How to test this

1. Navigate to the DAST scanner profile page in your GDK:

/:namespace/:project/-/security/configuration/dast_profiles/dast_scanner_profiles/new

2. Select cancel button

3. It should redirect to /:namespace/:project/-/security/configuration/dast_scans/#scanner_profiles

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• 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