Update security_pipeline_execution_project_schedules when policy changes

Previously to !180714 (merged), security_pipeline_execution_project_schedules would read the frequency (cron) directly from the policy and calculate the next run based on this. With this information now stored with the schedules, we also need to update them if the policy changes.