chore: upgrade protobuf to v2 and fabric protos in copm

[LordKubaya]

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.

[VRamakrishna]

LGTM. But let's treat this as a work in progress and make a refactor plan. We will need to refactor the code base to eliminate redundant proto definitions, which are currently copied over from weaver/common/protos to various packages touched in this PR. @LordKubaya Can you open an issue to track this?

[sandeepnRES]

We were using release-2.1 branch of fabric-protos repo (so as to not cause any build breaks from new changes). But if latest release is compatible, then we can use that, but I'll prefer to use some branch/tag of fabric-protos and not main branch.

[sandeepnRES]

PR looks good to me, just one comment I feel is important, its a small change. but you will have to test compatibility

[LordKubaya]

PR looks good to me, just one comment I feel is important, its a small change. but you will have to test compatibility

Changed to release 2.1, there are no problems.

[LordKubaya]

LGTM. But let's treat this as a work in progress and make a refactor plan. We will need to refactor the code base to eliminate redundant proto definitions, which are currently copied over from weaver/common/protos to various packages touched in this PR. @LordKubaya Can you open an issue to track this?

#4086

[VRamakrishna]

@outSH @RafaelAPB @AndreAugusto11 Can any of you review and approve so Carlos can merge this soon and move to the next task? Thanks!