Support resource machine client library in the nock backend

[paulcadman]

Requirement

The Anoma client provides a library in the client proving context which includes functions to:

• Generate proofs
• Create commitments and nullifiers

This will be provided in the environment slot of a transaction function when it is applied.

Say the transaction function is some nock code [code args env] then when it is applied then the args slot is replaced by the application arguments and the env slot is replaced by the nock code of the resource machine standard library.

The hoon version of the incomplete library is available: https://github.com/anoma/anoma/blob/39c84b01f6af6c0167c67fe6eabc7450464ac5e4/hoon/resource-machine.hoon

We require that the functions defined in this client library are made available to application function authors in frontend Juvix syntax (via builtins).

Implementation

We should use a similar strategy that we use for Anoma Nock standard library calls:

• https://github.com/anoma/juvix/blob/main/src/Juvix/Compiler/Nockma/StdlibFunction.hs

Specifically we need to:

• Record the nock path offsets for each function in the resource machine client library in a compiler data structure.
• Capture the client library from the function environment in a similar way to how we capture the scry id from the transaction function arguments.
• Add frontend builtin calls that call each of the client functions, in a similar way to callStdlib works now.