feat(copm): add Corda COPM implementation

[jenniferlianne]

Primary change:

Implements COPM primitives for Corda as a cacti plugin. The implementation follows the model of the Corda ledger connector plugin, where a typescript pass-through implementation is registered on the plugin server, and commands are implemented on a separate grpc server in the Kotlin Spring framework.

Secondary changes:

• The lock claim protobuf structure was updated to reduce the number of parameters.
• A no-op endpoint was added, per project specification
• The format of the inter-network command for requesting the status of a pledge varies by remote network type and asset. Adds a function to the typescript interop configuration interface to supply the appropriate command given the remote network and asset.
• Adds test package to test combinations of network types
• Updates CI script to use new testing framework
• Updates linter ignore to include weaver build directories, allowing yarn lint to pass on a system where weaver libraries have been built. Also excludes docs directory to avoid linting minified js from documentation packages.

Pull Request Requirements

• [x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• [x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• [x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• [x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• [x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners For rebasing and squashing, here's a must read guide for beginners.

[jenniferlianne]

@jenniferlianne Looking pretty high quality in general, but as usual I have some requests. On top of the comments I left inline, please make sure to include a test case which verifies the plugin being functional while used through the API server (you'll most likely need a separate package because this one cannot depend on the API server due to circular dependency issues) If you need examples just let me know.

As mentioned on the call, the plugin is brought up via the ApiServer in both fabric and corda cases. Please see: packages/cacti-copm-test/src/main/typescript/corda/copm-tester-corda.ts line 118 packages/cacti-copm-test/src/main/typescript/fabric/copm-tester-fabric.ts line 122

[sandeepnRES]

@jenniferlianne Thank you for the PR, overall looks good to me. Just some small suggestions above I've shared.