Add tezos signer service

[denisandreenko]

The tezos signer service will be running as a part of the FF stack for tezos flow which is responsible for transactions signing process

[codecov-commenter]

Codecov Report

Merging #1416 (87c938b) into main (b3443ec) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1416   +/-   ##
=======================================
  Coverage   99.99%   99.99%           
=======================================
  Files         321      321           
  Lines       23027    23027           
=======================================
  Hits        23025    23025           
  Misses          1        1           
  Partials        1        1           

[nguyer]

I don't think Signatory needs to go in the manifest.json. Currently, the manifest.json is used for the following two reasons:

• Lists the images/tags of FireFly services (within the Hyplerledger project) that should be tested together
• Lists the images/tags of the containers used to compile FireFly core and its smart contracts

Currently, we do not list other third party services that may be required in some configurations. For example, we don't list specific versions of Besu, Geth, Fabric, etc. We also don't list a specific Postgres image, even though it is a requirement if you're not using SQLite. I tend to think of Signatory as falling in the same bucket. It's a runtime that is outside the project, but may be required as a runtime dependency in certain configurations.

In reality, FireFly is probably compatible with a wide range of versions of these services and we want to allow end users to upgrade FireFly independently of third-party services. The idea behind the manifest.json is if you are going to upgrade FireFly here is the list of images that you should upgrade. How and when you upgrade third party services is up to you.