gRPC: Add decoded PlutusData and NativeScript in proto definition

[carbolymer]

Changelog

- description: |
    Add decoded PlutusData and NativeScript in proto definition #947 
# uncomment types applicable to the change:
  type:
   - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
   - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...
# uncomment at least one main project this PR is associated with
  projects:
  # - cardano-api
  # - cardano-api-gen
   - cardano-rpc
  # - cardano-wasm

Context

Previously, NativeScript and PlutusData were omitted in the ReadUtxos query feature:

• b2c9cea

This PR adds decoding of those values to the protobuf type. Using protobuf-defined values instead of CBOR blobs is advantageous, as it lets UTxO RPC consumers work with a single data format.

A rountrip property test is included.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. See Running tests for more details
• Self-reviewed the diff

[palas]

I think it is all accurate except for the bigint representation, which I am sure you already considered. But I commented on the bits that I found suspicious, even though I think they are all correct

[Jimbo4350]

This LGTM however you should start implementing round trip tests for your Inject instances and consider having a separate type class for these transformations.

I'll approve once the round trip tests are added.

[github-advanced-security]

hlint found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[Jimbo4350]

LGTM!

[Jimbo4350]

Why is there a uint32 field here?

[carbolymer]

That's how plutus encodes constructors with different numbers of of attributes. The tag can store values described here https://github.com/IntersectMBO/plutus/blob/fc78c36b545ee287ae8796a0c1a7d04cf31f4cee/plutus-core/plutus-core/src/PlutusCore/Data.hs#L80 and anything larger goes into the second field any_constructor.

[Jimbo4350]

Can you add a comment explaining the intention behind the 3 different fields here?

[carbolymer]

Pushed explanation upstream, I'll pull the changes to our repo later. utxorpc/spec@3a59863 (part of utxorpc/spec#177 )