[Feature Request]: Lower log-level for caught error in StorageApiWritesShardedRecords

### What would you like to happen?

We log an error here:
https://github.com/apache/beam/blob/e5e3cb25ca4fc2e31c10eb3dbda8289c6bfc7140/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/StorageApiWritesShardedRecords.java#L447-L448

But I've seen that these errors can be benign, e.g. `ALREADY_EXISTS: The offset is within stream, expected offset ...` can happen when re-establishing a stream, but doesn't indicate a failure, so logging it as an error is misleading.

### Issue Priority

Priority: 2

### Issue Component

Component: io-java-gcp