Service instance remains in whatever state it was on an exception

[shadeofblue]

Description

OS: any
[ e.g. Ubuntu 18.04, Windows 10, etc ]

yapapi library version: 0.7.0dev

Description of the issue:
When an error occurs on an Service instance, the state of the instance remains what it was, e.g. running or starting instead of being transitioned to terminated

Actual result:

[2021-09-17T13:08:41.590+0200 INFO yapapi.summary] [Job 1] Task started on provider 'EBGolem-1', task data: Service: SimpleService
[2021-09-17T13:08:41.882+0200 INFO yapapi.summary] [Job 1] Terminated agreement with EBGolem-1
[2021-09-17T13:08:43.289+0200 INFO yapapi.summary] [Job 1] Accepted invoice from 'EBGolem-1', amount: 0
instances: ['simple-service-1: starting on EBGolem-1']

Steps To Reproduce

1. introduce an error in the Service code, e.g.

SomeService(Service):
    async def start():
        pass

2. run a script that launches that service with Golem.run_service
3. observe the behavior -> the Service instance remains started despite a clear indication of termination of the activity

Expected behavior

The service should be marked terminated