refactor ratio

[nandotorterolo]

Purpose

Question; is there a reason why this https://github.com/Topl/protobuf-specs/blob/main/proto/node/models/ratio.proto pb spec was added to the node package?
I ask because I was looking at the definition of UpdateProposal, and I think it may introduce a circular dependency across packages (node depends on brambl, brambl depends on node). But maybe I am missing something and it was intentional and not an issue

Approach

• moved to quivr shared.

Note

• scala-Protobuf compiler does not show any warning or error about circular dependency, which I am not sure If it is really a circular dependency.
• In case we procced with this refactor we will need to update the Node.
• any other suggested place to move it?

Tickets

BN-1248

[SeanCheatham]

I think it's okay to make this change since a Ratio might be a useful primitive in Quivr at some point anyway. Technically I don't think there are circular dependency issues with it right now, but if you think there might be in the future, it's better to move it sooner than later.