feat(x/data): query iri by hash cli and rest endpoint

[ryanchristo]

Description

Closes: #1087

This pull request adds a CLI command to query IRI by content hash using a json file as well as the ability to query IRI by raw and graph content hash properties using a gRPC REST endpoint.

CLI Command

./build/regen q data iri content.json

{
  "graph": {
    "hash": "YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=",
    "digest_algorithm": "DIGEST_ALGORITHM_BLAKE2B_256",
    "canonicalization_algorithm": "GRAPH_CANONICALIZATION_ALGORITHM_URDNA2015",
    "merkle_tree": "GRAPH_MERKLE_TREE_NONE_UNSPECIFIED"
  }
}

REST Endpoints

curl "localhost:1317/regen/data/v1/iri-by-raw?hash=YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=&digest_algorithm=1"

curl "localhost:1317/regen/data/v1/iri-by-raw?hash=YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=&digest_algorithm=DIGEST_ALGORITHM_BLAKE2B_256"

curl "localhost:1317/regen/data/v1/iri-by-graph?hash=YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=&digest_algorithm=1&canonicalization_algorithm=1"

curl "localhost:1317/regen/data/v1/iri-by-graph?hash=YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=&digest_algorithm=DIGEST_ALGORITHM_BLAKE2B_256&canonicalization_algorithm=GRAPH_CANONICALIZATION_ALGORITHM_URDNA2015"

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[codecov]

Codecov Report

Merging #1107 (acef633) into master (484eeca) will increase coverage by 0.50%.
The diff coverage is 97.02%.

@@            Coverage Diff             @@
##           master    #1107      +/-   ##
==========================================
+ Coverage   68.44%   68.95%   +0.50%     
==========================================
  Files         212      213       +1     
  Lines       21390    21742     +352     
==========================================
+ Hits        14641    14992     +351     
+ Misses       5425     5418       -7     
- Partials     1324     1332       +8     

Flag	Coverage Δ
experimental-codecov	68.82% <97.02%> (+0.48%)	⬆️
stable-codecov	63.08% <97.02%> (+0.68%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[ryanchristo]

cc @paul121 if you want to take a look as well.

[aleem1314]

lgtm

[technicallyty]

pre-approving, few nits 👍🏻

[technicallyty]

👀

[ryanchristo]

98ceb6f

[technicallyty]

should be able to use ErrorContains here

[ryanchristo]

bz is the response from GetRequest so we are checking if the error message is within the get response. The err above is from UnmarshalJSON. ErrorContains requires an error type and cannot be used with json.

[technicallyty]

ditto

[ryanchristo]

Same as above. We need to check if the response contains the error message.

[technicallyty]

just curious, why do we do the replace?

[ryanchristo]

For REST endpoints, we cannot use + in the param value so it needs to be encoded.