chore: Remove outdated documentation about testing iox client crate
Looks like the type of integration testing referenced in the docs
deleted here was removed in
@@ -29,22 +29,3 @@ stores. Use the same bucket name when setting up the different services.
Other than possibly configuring multiple object stores, configuring the tests to use the object
store services is the same as configuring the server to use an object store service. See the output
of `influxdb_iox run --help` for instructions.
-
-## InfluxDB IOx Client
-
-The `influxdb_iox_client` crate might be used by people who are using a managed IOx server. In
-other words, they might only use the `influxdb_iox_client` crate and not the rest of the crates in
-this workspace. The tests in `influxdb_iox_client` see an IOx server in the same way as IOx servers
-see the object store services: sometimes you'll want to run the tests against an actual server, and
-sometimes you won't.
-
-Like in the `object_store` crate, the `influxdb_iox_client` crate's tests use the
-`TEST_INTEGRATION` environment variable to enforce running tests that use an actual IOx server.
-Running `cargo test -p influxdb_iox_client` will silently pass tests that contact a server.
-
-Start an IOx server in one terminal and run `TEST_INTEGRATION=1
-TEST_IOX_ENDPOINT=http://127.0.0.1:8080 cargo test -p influxdb_iox_client` in another (where
-`http://127.0.0.1:8080` is the address to the IOx HTTP server) to run the client tests against the
-server. If you set `TEST_INTEGRATION` but not `TEST_IOX_ENDPOINT`, the integration tests will fail
-because of the missed configuration. If you set `TEST_IOX_ENDPOINT` but not `TEST_INTEGRATION`, the
-integration tests will be run.
