Update to elasticsearch 1.1.0

Closes #18.
Run tests with only one JVM

(cherry picked from commit d003f39)
Fix typo
prepare release elasticsearch-cloud-gce-2.1.0
prepare for next development iteration
Upgrade to GCE v1-rev15-1.18.0-rc API

Closes #19.
Fix log

Related to #19.
(cherry picked from commit 89c29c4)
Fix tests when running mvn tests
(cherry picked from commit 1edd72e)
prepare release elasticsearch-cloud-gce-2.1.1
prepare for next development iteration
Create branch es-1.2

(cherry picked from commit 314b146)
Update to elasticsearch 1.2.0

Closes #21.
NPE when no tags on instance

When no tags exists on other running instances and if we try to filter by tag, we get the following error:

```
[2014-05-19 16:17:37,377][DEBUG][discovery.gce            ] [Theresa Cassidy] start building nodes list using GCE API
[2014-05-19 16:17:37,378][INFO ][cloud.gce                ] [Theresa Cassidy] starting GCE discovery service
[2014-05-19 16:17:37,592][TRACE][discovery.gce            ] [Theresa Cassidy] gce instance hadoop1 with status RUNNING found.
[2014-05-19 16:17:37,597][TRACE][discovery.gce            ] [Theresa Cassidy] start filtering instance hadoop1 with tags [elasticsearch, dev].
[2014-05-19 16:17:37,597][TRACE][discovery.gce            ] [Theresa Cassidy] comparing instance tags null with tags filter [elasticsearch, dev].
[2014-05-19 16:17:37,597][WARN ][discovery.gce            ] [Theresa Cassidy] Exception caught during discovery java.lang.NullPointerException : null
[2014-05-19 16:17:37,597][TRACE][discovery.gce            ] [Theresa Cassidy] Exception caught during discovery
java.lang.NullPointerException
    at org.elasticsearch.discovery.gce.GceUnicastHostsProvider.buildDynamicNodes(GceUnicastHostsProvider.java:157)
    at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.sendPings(UnicastZenPing.java:245)
    at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$2.run(UnicastZenPing.java:176)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
[2014-05-19 16:17:37,598][DEBUG][discovery.gce            ] [Theresa Cassidy] 0 node(s) added
[2014-05-19 16:17:37,598][DEBUG][discovery.gce            ] [Theresa Cassidy] using dynamic discovery nodes []
```

Closes #22.
Update instructions for GCE

Some tools have changed on GCE platform.
We need to update the documentation.

Closes #23.
Update to elasticsearch 1.3.0

Closes #24.
Fix tests

When upgrading to elasticsearch 1.2.1 test framework, some tests are not working anymore because of
`ElasticsearchIntegrationTest#ensureClusterSizeConsistency()` method which check that the number of started nodes
is the number of available nodes in the cluster.

Disabling them temporary.

Also, a new clientNode could be added (depends on seed). It adds a node more than expected.

(cherry picked from commit bcc2cd5)
Docs: make the welcome page more obvious

Closes #31.
Included notes about compute engine permissions

Closes #25.
Closes #26.

(cherry picked from commit 0db6959)
Force Token URL to `http://metadata.google.internal/...`

In certain environments (such as inside a docker container) 'metadata' does not resolve.
Forcing URL to `http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token` fix this.

See https://developers.google.com/compute/docs/metadata#metadataserver

Closes #28.
Closes #30.

(cherry picked from commit 8bd7e42)
Update to Lucene 4.9.0

Closes #32.

(cherry picked from commit 3dcc512)