TimersManager: Start timer post launch hook

[iLLiCiTiT]

Brief description

Currently only post launch hook starting timer is in Ftrack but it can be triggered using TimersManager.

Changes

• added new post launch hook using webserver to start timer for passed context
• ftrack post launch hook does not start timer
• removed need of "hierarchy" in rest api call to start timer
• replaced not used change_timer_from_host with static method start_timer_with_webserver

Resolves #1656

[mkolar]

Task linked: OP-1172 Start timer post launch hook

[kalisp]

Its working.

I am just wondering if check for context (project_name, asset_name, task_name) shouldn't be part of the calling function. Is there any use case where context could be empty or would I add validation for context whenever I would like to use the start_timer_with_webserver ?

[iLLiCiTiT]

Is there any use case where context could be empty or would I add validation for context whenever I would like to use the start_timer_with_webserver ?

I don't think that there is a use case when client side could handle that in any way. I mean if you find out that context you want to use is invalid what will you do with that? But it does make sense to return "success" in response. And add validate context method but I would not call it automatically in start_timer_with_webserver.