Add new route for DAST Profile Library

Related issue - #356697 (closed)

What does this MR do and why?

• Adds a new route profile_library which is an alias of dast_scans

Follow-ups

• Migrate all existing usages to the new alias (profile_library) - !84945 (merged)

• Remove the old route (dast_scans) - #358797 (closed)

This is primarily done to align the routes with the product naming. We recently did some related copy changes in #355316 (closed).

Screenshots or screen recordings

No visual changes for the user

before	after (notice the address bar for route change)

• Old route: http://gdk.test:3000/flightjs/Flight/-/security/configuration/dast_scans
• New route: http://gdk.test:3000/flightjs/Flight/-/security/configuration/profile_library

How to set up and validate locally

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.