VMware vSphere Integrated Containers provider (#206)

* Add Virtual Kubelet provider for VIC

Initial virtual kubelet provider for VMware VIC.  This provider currently
handles creating and starting of a pod VM via the VIC portlayer and persona
server.  Image store handling via the VIC persona server.  This provider
currently requires the feature/wolfpack branch of VIC.

* Added pod stop and delete.  Also added node capacity.

Added the ability to stop and delete pod VMs via VIC.  Also retrieve
node capacity information from the VCH.

* Cleanup and readme file

Some file clean up and added a Readme.md markdown file for the VIC
provider.

* Cleaned up errors, added function comments, moved operation code

1. Cleaned up error handling.  Set standard for creating errors.
2. Added method prototype comments for all interface functions.
3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder.

* Add mocking code and unit tests for podcache, podcreator, and podstarter

Used the unit test framework used in VIC to handle assertions in the provider's
unit test.  Mocking code generated using OSS project mockery, which is compatible
with the testify assertion framework.

* Vendored packages for the VIC provider

Requires feature/wolfpack branch of VIC and a few specific commit sha of
projects used within VIC.

* Implementation of POD Stopper and Deleter unit tests (#4)

* Updated files for initial PR

vendor/github.com/vmware/vic/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+<!--
+Thank you for submitting a pull request!
+
+Here's a checklist you might find useful.
+[  ] There is an associated issue that is labelled
+[  ] Code is up-to-date with the `master` branch
+[  ] You've successfully run `make test` locally
+[  ] There are new or updated unit tests validating the change
+
+Refer to CONTRIBUTING.MD for more details.
+  https://github.com/vmware/vic/blob/master/.github/CONTRIBUTING.md
+-->
+
+Fixes #
+
+<!--
+To trigger a custom build with this PR, include one of these in the PR's body:
+- To skip running tests (e.g. for a work-in-progress PR), add `[ci skip]` or `[skip ci]`
+to the commit message or the PR title.
+- To run the full test suite, use `[full ci]`.
+- To run _one_ integration test or group, use `[specific ci=$test]`. Examples:
+  - To run the `1-01-Docker-Info` suite: `[specific ci=1-01-Docker-Info]`
+  - To run all suites under the `Group1-Docker-Commands` group: `[specific ci=Group1-Docker-Commands]`
+- To skip running the unit tests, use `[skip unit]`.
+- To fail fast (make normal failures fatal) during the integration testing, use `[fast fail]`.
+-->