[Feature]: Allow to specify `max_duration` for dev environments and tasks

[r4victor]

Problem

Dev environments have no lifetime limits, which means they can sit idle until you stop them. If you are not careful, it may lead to an unexpected cloud bill. The same problem may occur with forever-running tasks.

Solution

Profiles get max_duration property. The runner stops the dev environment/task if max_duration is exceeded. max_duration is set to reasonable default values for dev environment and tasks – I suggest 6h and 72h. It should be possible to set max_duration to "off".

Benefit

Protect from idle instances.

Alternatives

Would you like to help contributing this feature?

Yes