[Feature Request]: Add the job id to userAgentString for Spanner IO

[liferoad]

What would you like to happen?

https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/spanner/SpannerAccessor.java#L231

We could add more information such as the job id to userAgentString to help trace the spanner issue.

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[stephenmw]

I talked with @liferoad offline. I think we should use job ID instead of job name. Job IDs are globally unique making them easier to work with and contain no user generated content. The only downside is that they aren't available during graph construction and job submission. That is unlikely to be an issue during debugging.