Include scheduled security pipeline for Auto DevOps

Problem

Users who don't have a scheduled pipeline for security scanning jobs will have unintentionally put their projects at risk as well as have incomplete or out-of-date data in their security reports and dashboards.

Solution

With Auto DevOps, users get access to Auto-SAST, Auto-Dependency scanning... etc,. We should include a scheduled pipeline to run these jobs for users who have Auto DevOps. We can set the schedule to run once a week and the user can adjust it later if they require.

The goal is to get the user over the initial hurdle of setting-up the scheduled security pipeline and reinforce the practice of having a scheduled pipeline specific for security.