feat(cat-gateway): Add document endpoints

[stevenj]

Description

Adds the Signed Document endpoints

Related Issue(s)

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 370/370}$ | ${\color{red}Fail: 0/370}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 370/370}$ | ${\color{red}Fail: 0/370}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 370/370}$ | ${\color{red}Fail: 0/370}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 370/370}$ | ${\color{red}Fail: 0/370}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 370/370}$ | ${\color{red}Fail: 0/370}$ |

[neil-iohk]

@stevenj Following our conversation earlier I took a look here again, you mentioned using jsonrpc for our API, if so are we going to follow a specific version like 2.0 https://www.jsonrpc.org/specification.

While the spec doesn't explicitly say that method is required it is inferred based on the rest of the context around request format like params where it states it MAY be omitted, if we are following this spec, what approach do you want to take to specify the method, a single document method, or more granular depending on usecase? Should these be defined along with the actions, while they may not be entity specific and more general a list of these may help cover a lot of the usecase examples listed in the API doc.

Depending on the approach here I will hold off updating anything to reflect discussions this morning and I can move relevant API sections into the docs later

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 371/371}$ | ${\color{red}Fail: 0/371}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 371/371}$ | ${\color{red}Fail: 0/371}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 373/373}$ | ${\color{red}Fail: 0/373}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 373/373}$ | ${\color{red}Fail: 0/373}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 385/385}$ | ${\color{red}Fail: 0/385}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 381/381}$ | ${\color{red}Fail: 0/381}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 385/385}$ | ${\color{red}Fail: 0/385}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 386/386}$ | ${\color{red}Fail: 0/386}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 390/390}$ | ${\color{red}Fail: 0/390}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 390/390}$ | ${\color{red}Fail: 0/390}$ |

[github-actions]

❌ Test Report | ${\color{lightgreen}Pass: 386/387}$ | ${\color{red}Fail: 1/387}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 387/387}$ | ${\color{red}Fail: 0/387}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 387/387}$ | ${\color{red}Fail: 0/387}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 387/387}$ | ${\color{red}Fail: 0/387}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 387/387}$ | ${\color{red}Fail: 0/387}$ |

[Mr-Leshiy]

LGTM

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 390/390}$ | ${\color{red}Fail: 0/390}$ |