There is some variation in jsonnet "result" conventions.  This change
assumes the top level is a JSON object, and then walks down looking
for objects with `apiVersion` & `kind` fields.

While walking down, the current code will expand JSON arrays, and
object values.

In particular, this should correctly accept:
- single-value JSON files
- arrays (jsonnet --yaml-stream)
- "filename->object" objects (jsonnet --multi)

(Note that any v1.Lists encountered are still expanded in a
second-pass, as before)

travis.yml: Build linux release builds using a musl/C++ toolchain

Add missing vendored library

govendor fetch github.com/emicklei/go-restful/swagger@v1.2

Rename backsplice -> ksonnet

Rename early and often.

Implement "update" subcommand

- Support the standard client-go/kubectl flags
- Switch object types to use client-go rather than apimachinery
- Implement update subcommand

Rename package path bitnami/kubecfg -> backsplice/kubecfg

File format is recognised via simple file extension check.

Any "List" objects found will be expanded into their constituent
items, so single-element formats like json and jsonnet can use a
v1.List to capture multiple resource objects.

Repo was (at least initially) published under bitnami/ - make imports
consistent with that path.

Basic skeleton.  Can evaluate jsonnet and show the output as yaml or
json .. and that's about it.