feat: use structured concurrency for tss processes

[mpetrun5]

This PR implements:

• switch to go 1.19 (needed for the conc library) for syntax sugar
• refactor coordinator and tss processes to use structured concurrency and fix all not closed routines
• remove concurrency where not needed (handle of refresh and keygen events)

Sorry for the big change, but there were some problems with memory leaks before so wanted to make sure everything is properly cleaned up now when running singing, keygen and refresh.
@keks

The long running routines in the tss process are now running under the same context pool of routines and when 1 errors out or cancel is called manually they are all closed.
ExecuteProposals function now waits until coordinator Execute is over which waits until tss process is finished.

Related Issue Or Context

Closes: #159

How Has This Been Tested? Testing details.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation

[github-actions]

Go Test coverage is 66.6 %\ ✨ ✨ ✨

[keks]

Hey all, I have looked at the structured concurrency changes and I think think this is on a good path. My main comments relate to the way the goroutines are started around the TSS code (they do not only apply to the keygen code but resharing.go and signing.go as well). Also there still is an error channel being passed around, which could probably be removed by just returning the error.

I left some more comments in other places that I think would further improve the robustness of the concurrent code.

[github-actions]

Go Test coverage is 66.7 %\ ✨ ✨ ✨

[github-actions]

Go Test coverage is 66.9 %\ ✨ ✨ ✨

[mpetrun5]

Hey all, I have looked at the structured concurrency changes and I think think this is on a good path. My main comments relate to the way the goroutines are started around the TSS code (they do not only apply to the keygen code but resharing.go and signing.go as well). Also there still is an error channel being passed around, which could probably be removed by just returning the error.

I left some more comments in other places that I think would further improve the robustness of the concurrent code.

Hey, thanks for the comments.
Refactored the tss process so it returns an error now.
Please take another look.

[bashirabuamr]

Hey @MakMuftic @keks is unavailable for the time being, however he passed along that the PR looks good to approve. If you want to add me @bashirabuamr I can approve it on his behalf. We will mark it resolved in the Final Audit Report.

[github-actions]

Go Test coverage is 67.0 %\ ✨ ✨ ✨

[github-actions]

Go Test coverage is 67.0 %\ ✨ ✨ ✨