Py310 fix

[malkaed]

When running workers, Activity task worker and Decision task worker throw an asyncio.CancelledError error the first time they are started(not sure why), in python 3.7, the retry decorator excepts that error using except Exception and trys to restart the worker which solves the issue.
In python 3.8, asyncio.CancelledError became a subclass of BaseException instead of Exception, so the error is no longer excepted and is raised instead, causing the workers to not start.
The previous commit solved this issue for the Activity task worker, but not for the Decision task worker(which failed for our case), this PR solves both issues by adding handling of the asyncio.CancelledError error to the retry decorator so that it would behave exactly as it did in python 3.7.
Handling of asyncio.CancelledError is separated from handling of Exception to not call logger.error().

[NullOsama]

It was working fine on local, but I got lots of unhandled exceptions during testing those changes on stg. See link and link. In the previous commit the log.error was omitted, So maybe you can catch the asyncio.CancelledError in a different block and just sleep initial time.