Fix link errors in build tests
This appears to only be a problem with gcc/ld builds. When using clang/lld the build succeeds. Hi @cheshire Can you please review this PR ? Thank you! TF has a canonical build configuration, and OSS CI is passing, why should this change be required? @cheshire It fails when building with gcc toolchain. AFAIK the policy is to accept patches that are for gcc fixes. Then there should be a GCC CI? @cheshire Please see the [SIG BUILD notes](http://bit.ly/tf-sig-build-notes) from 2nd May 2023, with the comment about "we'll accept PRs to fix gcc!" @cheshire Indeed, this is a special case. Although TF's official builds now use and are gated by clang, we (the TF DevInfra team) decided to keep accepting changes that help make TF able to build with GCC, since a large portion of TF's community builders still use gcc for their platforms. We currently leave verification up to them.    This sounds like a difference with `-Was-needed`, not actually due to clang/gcc. I wouldnt be surprised if you added as-needed on clang it'd fail as well. Maybe `:stream_executor_pimpl` needs to have `alwayslink=True` set?
 Hi @elfringham Can you please resolve conflicts? Thank you! Due to the delays in getting this merged, it is now too late as the code has been moved to a different repo.
Some build tests were failing due to unresolved symbols so add in their dependencies