bazel: expand linkstamp beyond binary rules.

[junr03]

bazel: expand linkstamp beyond binary rules.

Description: linkstamp is currently used by the VersionInfo class to stamp envoy binaries. This is a robust mechanism. However, there are two current problems with it:

1. It is poorly documented and understood. Document git workspace SHA1 inclusion in C++ builds bazelbuild/bazel#2893
2. linkstamp is not available for non-binary rules. Thus if the version_info_lib is compiled outside of a top-level binary rule the linker will not be able to find symbols defined by the linkstamp rule. For now this is resolved by VersionInfo: allow non-linkstamp rules to link in definitions #6803. However, it would be great to use the same, robust linkstamp mechanism we use for binary rules.

[junr03]

cc @htuch lmk if this is sufficient for the bazel folks, or if you'd like me to open an issue against bazel.

[htuch]

@junr03 it's sufficient for me to share, thanks. I think if we want action on the Bazel front though, it would be good to have a tracking issue in their GH.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.