Add DAST configuration page to DAST Profiles redirection logic

Related epic - &5981 (closed)

What does this MR do?

This is an UX improvement to redirect user to previous page after updating DAST Profiles. This MR

• Adds option to allow multiple paths to the redirection logic
• Allow DAST Configuration page

Screenshots (strongly suggested)

• No changes for end users; this MR is to facilitate future changes related to DAST Configuration in &5981 (closed)

• See attached screencast to get some context around the redirection flow

  • upon profile updation, it redirects user back to the previous page
  • pre-populate the profile which got updated

dast_redirection

Does this MR meet the acceptance criteria?

Conformity

• [-] I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
• [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.