Add ability to disable ZetaClient functionality at run time

[lumtis]

Describe the Issue

The following PR introduces test for inbound trackers: #3179

To effectively test trackers, the observation should be disable, the current solution is to disable in the code observation logic with an early return.
This solution is not scalable and doesn't allow to test in the CI (at least properly)

We should be able to disable through config or so functionality such as inbound observation at runtime.

So the inbound tracker test can be integrated in the CI

• start e2e test
• disable inbound observation
• run tracker test
• resume inbound observation

This is one example but the solution could be generalized to all the different functionality:

• inbound observation
• outbound observation
• TSS keysigning
• RPC watcher

Overall this would enable developer new class of E2E reliability test by simulating network downtime, etc...

Example:

• Disable inbound observation
• Run a large number of deposit
• Resume observation and check all deposit are observed