[WIP] 1st attempt for build peer cli

[SamYuan1990]

1st attempt for build peer cli

• peer and osadmin cli folder structure.
• some internal package refine.

todo:
if the folder structure looks good, then adding for all peer lifecycle command impl and end to end test case.

Contributes to #202

[SamYuan1990]

Hi @denyeart and @bestbeforetoday

I would like to have you reviewed with current WIP part of code as if I am moving on, this pr will be too large to review.
Hence I make current implementation with lifecycle install as an example for how it's going to be like.

Please let me know for your review comments.

Regards
Sam

[bestbeforetoday]

I think the approach generally looks good. Some suggestions:

• Name the commands as make sense in line with the fabric-admin-sdk rather that following the conventions of the existing peer command. I think everything just lived within the peer command because it was all baked into the peer binary. We can be more flexible, perhaps with an admin command a sub-commands like chaincode to align with the admin SDKs chaincode package. We could even have different CLI commands for different tasks, if that makes more sense.
• Align the command parameters and behaviour with the admin SDK rather than just following what is there in the existing peer CLI. There are cases where we might require less information because we are using the Gateway API internally, which handles aspects of endorsement without specifying a set of endorsing peers. We might also consider parallel operations, such as installing to a list of peers with a single CLI command.
• Avoid some of the legacy on-disk configuration files. Just take command-line parameters.