Krane 1.0 release

[dturn]

Problem

We're transitioning from kubernetes-deploy to krane. We need to update the gemspec, version to 1.0, and deploy to ruby gems under krane. This PR should be completed immediately after #527.

Possible solution

Update the gemspec, shipit.yml, and Version file. #631

Acceptance criteria

• Audit our public interfaces to ensure that arguments to each public function are sensible and consistent (same names for same thing, required vs. optional, on initialize vs on run). (Make task arguments match the new flag names #619)
• Delete everything "kubernetes-deploy" (Remove kubernetes-deploy* #622)
• StatsD Rename (Update StatsD Prefix #623)
• Ensure we have documented what our public interfaces are (and possibly what they are not) (Update the README to use krane instead of kubernetes-deploy #634)
• Ensure that all 1.0 tasks are complete or intentionally deferred.
• Datadog dashboards are updated for krane and kubernetes-deploy
• Migration guide is linked near the top of the readme. (Update the README to use krane instead of kubernetes-deploy #634)
• gem 'krane', '~> 1.0.0' works.

Additional context

#256 (comment)

[dturn]

As we transition to Krane 1.0. We'll create 1 or more kubernetes-deploy v1.0.0-pre.X releases. The final pre-release version will be a transition version that maintains backwards compatibility with kubernetes-deploy as well as have all of the Krane commands.

Krane 1.0.0 will not include any kubernetes-deploy modules or commands. We'll be publishing a transition guide.

[dturn]

Krane 1.0.0 has been released.