Oracle data integration

[JesseAbram]

This PR integrates oracle data into programs and implements block number as the first use case

• All oracle data is determined by the chain (how is up to specific implementation)
• Oracle data is stored in oracle_data in the Oracle pallet under a scale encoded key and scale encoded value (bounded vecs for both
• upon running a sig request the oracle data location is pulled from the ProgramInfo in the Programs pallet to know what heading the specific oracle data is under
• The data pulled from the chain is passed to the program for evaluation

Closes #789

[ameba23]

I've read over this and it all looks good.

But on a high level im still a bit unclear on the use case for oracles and how users who want to add an oracle data source would do that.

Are oracles supposed to be something which is fetched or computed at the point of making a signature request, or would the chain constantly retrieve data regardless of whether signature requests are made?

[ameba23]

Maybe it would be clearer to return program_info rather than a tuple

[ameba23]

Maybe make an issue

[JesseAbram]

I've read over this and it all looks good.

But on a high level im still a bit unclear on the use case for oracles and how users who want to add an oracle data source would do that.

Are oracles supposed to be something which is fetched or computed at the point of making a signature request, or would the chain constantly retrieve data regardless of whether signature requests are made?

the second one, then it gets fed into the program based on how the program is written. It can be a lot of data, but the "end game" for this as of now would be super cool to get ibc proofs on chain and then be able to give a proof of the state of a chain verify it in a program and use it as a constraint