feat(trigger): reload trigger if file changes

[Lee-W]

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[Lee-W]

Hi @uranusjr, I recall you mentioning that reloading is generally not a good idea. However, @pauloventurab faced a syncing issue with the triggerer on #31743. I'm not sure if there're other better solutions than reloading the triggerer. I have drafted an idea of reloading only when necessary in this draft PR. I would appreciate your feedback on it. Thank you.

[uranusjr]

I am very against this as well. This seems to solve the immediate problem, but will very likely to cause other issues down the road.

Why not just restart the triggerer process? The process is designed to be robust, and reloading it entirely is a fully supported operation.

[Lee-W]

I am very against this as well. This seems to solve the immediate problem, but will very likely to cause other issues down the road.

Yep, I guess that would be the case as well. That's why I'd like to have some feedback before investing more time crafting it 🙂 Thanks for the prompt feedback.

Why not just restart the triggerer process? The process is designed to be robust, and reloading it entirely is a fully supported operation.

If that's the case, should we comment on this solution on #31743, mark the issue as won't fix, and close it?

[uranusjr]

I’m thinking maybe (not sure) we can still do something to reduce the confusion. Let’s continue in the issue thread instead.

[Lee-W]

Got it. Sounds good 👍 I'll check what can be done to reduce such confusion. Thanks!