Fix hyperlane types

[jmcardon]

Fixes our hyperlane type definitions to include the correct type schemas, as well as exporting schemas for hyperlane definitions

That is, we go from:

pact> hyperlane-message-id 
native `hyperlane-message-id`

  Get the Message Id of a Hyperlane Message object.

  Type:
  x:object:* -> string

to

pact> hyperlane-message-id 
native `hyperlane-message-id`

  Get the Message Id of a Hyperlane Message object.

  Type:
  x:object:{hyperlane-token-msg} -> string

As well as exporting the two necessary schemas:

pact> hyperlane-token-msg
(defschema
hyperlane-token-msg
"Schema type for hyperlane messages"

[ version:integer
, nonce:integer
, originDomain:integer
, destinationDomain:integer
, recipient:string
, tokenMessage:object:(defschema
hyperlane-token-erc20
"Schema type for ERC20 TokenMessage"

[recipient:string, amount:integer]) ])
pact> hyperlane-token-erc20
(defschema
hyperlane-token-erc20
"Schema type for ERC20 TokenMessage"

[recipient:string, amount:integer])

PR checklist:

• [ ] Test coverage for the proposed changes
• [x] PR description contains example output from repl interaction or a snippet from unit test output
• [x] Documentation has been updated if new natives or FV properties have been added. To generate new documentation, issue cabal run tests. If they pass locally, docs are generated.

Additionally, please justify why you should or should not do the following:

• [ ] Confirm replay/back compat
• Will need replay
• [x] Benchmark regressions
• There are functionally no changes to any implementations
• [x] (For Kadena engineers) Run integration-tests against a Chainweb built with this version of Pact
• integration tests will need to be amended

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1206768107292131

[jmcardon]

Drafting until I receive some feedback on the hyperlane msg format

[rsoeldner]

closed for #1362