Hello, we would like to be able to handle triggers in git experience same as pipelines and input sets.

Currently everything but triggers is able to be maintained by git experience, leading to a situation where you think everything is managed in code, but it really is not and you are missing context as to how things work.

This is especially true when onboarding new engineers onto Harness and causes unnecessary confusion.

Thanks