Allow the disabling of Job Schedule support in Git

[jose_marquez1]

While CI/CD support for Job Schedules can be a useful feature, it is not always desirable.

It would be better if users could choose whether this is enabled for a workspace or via something like a .gitignore or perhaps .schignore for more fine-grained control.

[KimTutein]

My business case would be that we wish to have scheduling in git but a possibility to disable in for instance Test/Dev environments but then enable in production workspaces.

[BramT]

Yes I noticed last week that scheduling of pipelines is suddenly added in the Git repo, but we would have different schedules for DEV and PROD and for some environments no schedule at all. A .gitignore possibility would be helpfull.

[maturmel]

I too got surprised by the schedules now coming in the Git repo. Did not see that in the recent release notes. In my scenario I would have liked to keep that excluded from source control as I am setting up environments for dev, QA & pre-prod that are all connected to their own git branches. I am going to 'deploy' changes using PRs between these branches, as I need finer control over when to push what, where as Deployment Pipelines would only allow me to push, say an entire Warehouse, and I need to be able to select by tables/stored procs/ other SQL objects inside the Warehouse. But now with schedules being moved around in Git it kinda defeats my setup. And .gitignore is effectively ignored (ha!) by Fabric for that matter.