Fix object labels

[jt-nti]

MSP and peer ID annotations look like they might cause problems. Also potentially related to #88, can the object labels be improved to make management easier?

Valid label values:

• must be 63 characters or less (can be empty),
• unless empty, must begin and end with an alphanumeric character ([a-z0-9A-Z]),
• could contain dashes (-), underscores (_), dots (.), and alphanumerics between.

Possible label changes:

Key	Description	Current	Suggested
app.kubernetes.io/name	The name of the application	fabric	?
app.kubernetes.io/instance	A unique name identifying the instance of an application		?
app.kubernetes.io/version	The current version of the application (e.g., a SemVer 1.0, revision hash, etc.)		The ccid hash?
app.kubernetes.io/component	The component within the architecture		chaincode
app.kubernetes.io/part-of	The name of a higher level application this one is part of		fabric?
app.kubernetes.io/created-by	The controller/user who created this resource (deprecated)	fabric-builder-k8s
app.kubernetes.io/managed-by	The tool being used to manage the operation of an application	fabric-builder-k8s	fabric-builder-k8s
fabric-builder-k8s-mspid	Fabric peer MSP ID (may not be a valid label)	e.g. http://peer0.org1.example.com/	Use an annotation instead?
fabric-builder-k8s-peerid	Fabric peer ID (may not be a valid label)	e.g. Org1MSP	Use an annotation instead?

[jt-nti]

The following seem to work ok...

Labels:

• app.kubernetes.io/component=chaincode
• app.kubernetes.io/created-by=fabric-builder-k8s
• app.kubernetes.io/managed-by=fabric-builder-k8s
• app.kubernetes.io/name=hyperledger-fabric
• fabric-builder-k8s-cchash=N6MMJOZJIFDXCMJO3XI2QE7O6WB56IJBYI24I6LXSLYUDJDNJNCQ

Annotations:

• fabric-builder-k8s-ccid: go-contract:6f98c4bb29414771312eddd1a813eef583df2121c235c4797792f141a46d4b45
• fabric-builder-k8s-mspid: Org1MSP
• fabric-builder-k8s-peeraddress: host.minikube.internal:7052
• fabric-builder-k8s-peerid: peer0.org1.example.com

I also wonder whether adding a fabric-builder-k8s-cclabel label might be possible. The k8s builder would need to validate the package label to ensure it's a valid kubernetes label value. That would be a builder specific restriction, which doesn't seem unreasonable since it's inside a kubernetes package.