Integration tests should create/destroy resources required for running

By not creating/tearing down resources in integration tests, the tests are not portable or easily runnable by a user who doesn't have access to all the pre-created test artifacts.

For example BigtableReadIT assumes that it is executing in a project which has a specifically named Bigtable instance preloaded with testdata.

Also, KinesisReaderIT assumes an already created Kinesis topic exists.

Imported from Jira [BEAM-686](https://issues.apache.org/jira/browse/BEAM-686). Original Jira may contain additional context.
Reported by: lcwik.

Start by inspecting the BigtableReadIT and KinesisReaderIT integration tests, focusing on their assumptions about pre-created test artifacts. Identify how each test currently depends on existing resources and determine the setup and teardown needed. Done means the tests create and destroy their required resources and no longer require those pre-created artifacts.

Written by the indexing model from the issue text.