History entry labels

[seankelly001]

Describe the solution you'd like:
Ability to label history entries
e.g.
kconnect history label alias alias1 env=dev
kconnect history label --all env=dev

For import/export, also allow label to be applied
kconnect history export -f export.yaml -L env=prod

In batch run feature #228 , could enhance this by allowing all entries with a certain label to be run against the commands

apiVersion: kconnect.fidelity.github.com/v1alpha1
kind: RunConfig
metadata:
       name: run
spec:
 	selector:
            matchLabels:
                env: dev
 	commands:
 	- kubectl exec mypod -- somecommand
 	- kubectl logs mypod`

Why do you want this feature:
Would further enhance kconnects versatility and power, especially for ops teams needing to run commands against many clusters