Maven dependency conflicts between google-cloud-pubsub and Apache Beam packages

(I'm using BDD terminology to phrase the issue)

AS A DEVELOPER I want to be able to use the following Maven dependencies (or newer versions) in the same Java project inside Eclipse SO THAT I can subscribe to a Google pub/sub independently from the mechanism supplied by Apache Beam, and efficiently update a dataset linked to my Apache Beam dataflow.

I want to update my linked dataset by accepting push data that reflects changes to its data, instead of having to poll for new data each time I process an item from an Apache Beam pipeline that subscribes to a different Google pub/sub dataset.

 
```

com.google.cloud.dataflow
google-cloud-dataflow-java-sdk-all
2.5.0

com.google.cloud
google-cloud-pubsub

1.53.0

```

ACCEPTANCE CRITERIA

No dependency conflict related to io.grpc:grpc-core:jar is caused when I run
```

mvn clean install
```

against the project.

Please see here (I documented itas a GitHub issue against the google-cloud-pubsub library, however it's primarily a Beam Maven dependency issue):

[https://github.com/googleapis/google-cloud-java/issues/4095](https://github.com/googleapis/google-cloud-java/issues/4095)

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

Start by creating or locating a Java project with the listed google-cloud-dataflow-java-sdk-all 2.5.0 and google-cloud-pubsub 1.53.0 dependencies, then run mvn clean install. Inspect the io.grpc:grpc-core conflict and the linked google-cloud-java issue for context. Done means the project builds without a dependency conflict related to grpc-core.

Written by the indexing model from the issue text.