feat(cactus-connector-fabric): add get transaction receipt by tx id

[RafaelAPB]

Authored-by: Eduardo Vasques [email protected]
Co-authored-by: Rafael Belchior [email protected]
Signed-off-by: Rafael Belchior [email protected]

Pull Request Requirements

• 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.
• 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.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• 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.

[petermetz]

@RafaelAPB Please fix the DCO, otherwise looking good to me.

[RafaelAPB]

@petermetz fixed the PR according to your suggestions. I'm not sure why is the commit is unverified, because I'm signing the commit with a key whose public part is added to GPG keys' configuration space on Github

[petermetz]

@RafaelAPB I'm not sure what was wrong with the DCO but it's passing now so I'm OK.

Specifically to what you wrote: It's important to note that the GPG signing keys don't come into play at all from the DCO perspective.
The DCO is just a plain string comparison of the email in your commit message (the "signed-off by" line on the bottom) and the email that you have set up on your github account. So the email you have associated with your GPG key does not get examined at all.

[petermetz]

Oops, there's also a merge conflict, please let me know if you need help with that

[petermetz]

@hyperledger-cacti/cacti-maintainers bump