Move dynamic analysis vendored templates

What does this MR do and why?

Similarly to what has been done for other security products (see this MR), we start the migration of vendored templates from the Security folder into the more generic Jobs folder for Dynamic Analysis features.

In this MR we update the existing vendored templates in the Securit folder so that they point to the newly added ones in the Jobs folder

Notes:

• We keep Security reference in AutoDevOps template and doesn't change it.
• We don't change references in the documentation

WHY

TLDR it makes us closer to migrate out of Security subdir to align with the rest of the company and makes it a bit cleaner for people to include our features from the UI (at least until something like #24939 gets prioritized). The later is the main reason why Static Analysis did the move earlier as they were pushing for configuring SAST in core. This is well explained in #292977 (closed). I'm not a very big fan of the approach, but it is a borring solution until we have a proper way to correcly compose a Gitlab CI file from the UI.

See #352895 and #27825 (closed) for more context.

Describe in detail what your merge request does and why.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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.