upgrade grpc to v1.47.0

[pav-kv]

No description provided.

[pav-kv]

No need to merge to master, the branch stays in this repo, and the corresponding commit will be referenced.

[pav-kv]

Will create a new branch with no PR, because it's very tempting to press "Delete branch" in this PR at any time in the future.

[dt]

we typically fast forward push master to the referenced commit after the cockroachdb/cockroach PR referencing it merges at which point it is permanently going to be reachable from a protected branch; at that point you can delete the named branch

[pav-kv]

we typically fast forward push master to the referenced commit after the cockroachdb/cockroach PR referencing it merges at which point it is permanently going to be reachable from a protected branch; at that point you can delete the named branch

@dt What if crdb master rolls back to reference the previous commit of vendored? And then, say, upgrades to a different version. In this case we can't fast-forward vendored master, will have to move it to the forked branch, and leave a placeholder branch instead of the old master.

Does it never happen?

[dt]

vendored/master is protected, so if someone made a new vendored commit off of an older parent than the current head, you'd need a merge commit to push it

[pav-kv]

Makes sense, thanks @dt. Then my plan is to just merge this PR after cockroachdb/cockroach#88470 is merged. This will result in a fast-forwarded master in vendored as you suggested.

[dt]

perfect -- in the meantime it looks like nobody has pushed the currently crdb referenced commit to master here for awhile (meaning it isn't protected) so I'll do that real quick.

[pav-kv]

@dt thanks. I will rebase after you do it, this PR will nicely contain one commit then.