Add application limits to scheduled security scan execution

Why are we doing this work

Currently we have application limits for number of scheduled pipelines per project. Similarly, we should also have limits on number of scheduled pipelines created by security scan policies.

Relevant links

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

• database backend Add new column to plan_limits: security_policy_scan_execution_schedules,
• backend add include Limitable to Security::OrchestrationPolicyRuleSchedule and add self.limit_name = 'security_policy_scan_execution_schedules' and self.limit_scope = :project,

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.