Oracle verifier: migration to the new repository

[gangov]

Closes #2

[gangov]

that shows as

This branch has no conflicts with the base branch
Merging can be performed automatically. 

definitely not the case, anyway...

my current blocker is with the dependencies for cosmwasm-std; I've got issues with oracle-verifier using 1.5.7 while the avs-toolkit relies on 2.1.4;

if I try to bump up to version of cosmwasm-std for oracle-verifier-example then I have to get rid of

backtraces = ["cosmwasm-std/backtraces"]

I'm proceeding with backtraces disabled for now

[gangov]

okay, so I was able to make everything work (it's probably far from optimal, but we have something to improve from).

In summary: Cargo.toml in package

• because of their respective version in avs-toolkit we had to update the oracle-verifier depedencies for cosmwasm-* and cw-* to 2.0.0 or above that
• had to disable backtraces and golem

contract itself

• fixed some linting issues
• added lavs-helpers to make use of the new package and avoid duplication of code
• ensure_valid_vote takes in input arg called fraction_percent which initially wasn't present for the oracle-verifier so I added that to the InstatiateMsg and Config respectively, but something about it feels strange.

That's all for tonight, I will pick this up tomorrow morning with a fresh mind

[gangov]

will close #2

[ueco-jb]

I'm merging it as it is, because there's a lot of work to be done on top of it. Probably need further check regarding the task format and what it takes/returns.