datashare-python: configure worker timeouts (heartbeat + activity timeout) on the worker config side

[ClemDoum]

Currently timeouts (heartbeat + activity timeout) are either hardcoded in the code or configured through args however they should be configured on the worker side so that it's a deployment config not set by dev or user.

Currently we have to commit or set values through task inputs which is not the right way to set timeouts

[ClemDoum]

Potential priority for sprint 50: P0 quite blocking for iteration, settings timeouts in the code slows down iteration and multiplies releases