feat(spanner): implement generation and propagation of "x-goog-spanner-request-id" Header

[odeke-em]

In tandem this specification

https://orijtech.notion.site/x-goog-spanner-request-id-always-on-gRPC-header-to-aid-in-quick-debugging-of-errors-14aba6bc91348091a58fca7a505c9827

This change adds sending over the "x-goog-spanner-request-id" header
for every unary and streaming call, in the form:

<version>.<processId>.<clientId>.<channelId>.<requestCountForClient>.<rpcCountForRequest>

where:

• version is the version of the specification
• processId is a randomly generated uint64 singleton for the lifetime of a process
• clientId is the monotonically increasing id/number of gRPC Spanner clients created
• requestCountForClient is the monotonically increasing number of requests made by the client
• channelId currently at 1 is the Id of the client for Go
• rpcCountForRequest is the number of RPCs/retries within a specific request

This header is to be sent on both unary and streaming calls and it'll
help debug latencies for customers. On an error, customers can assert against
.Error and retrieve the associated .RequestID and log it, or even better
it'll be printed out whenever errors are logged.

Importantly making randIdForProcess to be a uint6 which is 64bits and not
a UUID4 which is 128bits which surely massively reduces the possibility of collisions
to ensure that high QPS applications can function and accept bursts of traffic
without worry, as the prior design used uint32 aka 32 bits for
which just 50,000 new processes being created could get the probability
of collisions to 25%, with this new change a company would have to
create 82 million QPS every second for 1,000 years for a 1% collision
with 2.6e18 for which the collision would be 1%.
Using 64-bits still provides really good protection whereby for a 1% chance of collision,
we would need 810 million objects, so we have good protection.
However, Google Cloud Spanner's backend has to store every one of the always on
headers for a desired retention period hence 64-bits is a great balance between collision
protection vs storage.

Fixes #11073

[odeke-em]

Kindly cc-ing @olavloite @tharoldD @willpoint

[odeke-em]

Kindly cc-ing you @harshachinta.

[rahul2393]

@odeke-em can you please fix the vet and tests issues here?