Extract useful Fabric proto utils into a separate Go module

[jt-nti]

From @davidkhala hyperledger/fabric-protos-go#10

It is a awesome direction that we split protobuf out from fabric itself.
Meanwhie in second development, fabric-protos-go is used frequently along with powerful tool github.com/hyperledger/fabric/protoutil
Would you consider also migrate github.com/hyperledger/fabric/protoutil to somewhere in github.com/hyperledger/fabric-protos-go

Perhaps fabric-lib-go would be a good home, and some thought about what to move is probably required since protoutil is currently a bit of a mixed bag.

[bestbeforetoday]

Any capability extracted out to a separate repository should probably also operate on fabric-protos-go-apiv2, not on fabric-protos-go.

[jt-nti]

It would definitely be preferable to use apiv2 but I think that depends on where/when it gets extracted, and what consumes the separate module, e.g. fabric-lib-go would probably need to use the old bindings until other components catch up.

[davidkhala]

@jt-nti @bestbeforetoday Any progres on this issue? Or did I miss something great?

[bestbeforetoday]

As far as I know, nobody is working on this. Somebody else might have better information.

[davidkhala]

@jt-nti @bestbeforetoday I have some free time to pick up this task recently, starting from here https://github.com/davidkhala/fabric-protoutil/, I copy the protoutil package to here and trying to isolating it from fabric core as much as possible.

Welcome comment on direction
@denyeart Dave, would you mind moving this to a github discussion?