File lock when flask/werkzeug is in debug mode

[indy-independence]

The file lock used by scheduler/scheduler.py to detect if a scheduler is already running is not working properly when flask/werkzeug is started with debug=True. When in debug mode the scheduler module seems to be loaded once, and then immediately reloaded, without releasing the file lock in between. This results in the scheduler starting with "is_mule = True" since it things a wsgi mule has already acquired the file lock. This is not a problem if running in wsgi mode (in docker etc) but only if you run in standalone API mode. Possible solutions:

• Make sure file lock is released when werkzeug does reload thing
• Use other method to determine if a scheduler is already started

Workaround: Set debug=False when starting werkzeug