docs: re-structure versioning.

This sorts docs a little differently than what happens currently.
Each key is a semver value/range. We would just specify pubsub in the array
for the versions it is valid for and not include it in the version(s) it
isn't valid for.

On Thursday, October 9, 2014, Ryan Seys <notifications@github.com> wrote:

> In docs/components/docs/docs-values.js:
>
> > @@ -62,8 +77,20 @@ angular.module('gcloud.docs')
> >      VERSIONS: {
> >        // Give a version with/without a comparator, anything semver:
> >        //   https://github.com/npm/node-semver#versions
> > -      // List should be in ascending order.
> > -      '<=0.7.1': ['gcloud', 'datastore', 'storage'],
> > -      '>0.7.1': ['gcloud', 'datastoreWithTransaction', 'pubsub', 'storage']
>
> In the past, we had to pull pubsub, if in the future, we need to do this,
> how can we show that using this format?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/gcloud-node/pull/254/files#r18685161>
> .
>