Add missing deps to integration test setup

[fmeum]

Fixes #25323
Fixes #25324
Fixes #25325
Fixes #25306

[fmeum]

@sgowroji

[mai93]

@fmeum will this also fix bazelbuild/examples#556?

[Wyverald]

I wonder if this'll cause any difficulties during import, but I guess we can't know without trying :)

[meteorcloudy]

https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4492#01953622-7720-4201-a255-1fb3970ec121
Still many tests failed with:

ERROR: cannot find bazel_tools/tools/bash/runfiles/runfiles.bash

[fmeum]

@meteorcloudy I can turn more filegroups into sh_librarys to fix this, but it's actually a bug in filegroup that swallows runfiles:

bazel/src/main/java/com/google/devtools/build/lib/rules/filegroup/Filegroup.java

Lines 93 to 98 in d5e62f1

	// If you're visiting a filegroup as data, then we also visit its data as data.
	new Runfiles.Builder(
	ruleContext.getWorkspaceName(), configuration.legacyExternalRunfiles())
	.addTransitiveArtifacts(filesToBuild)
	.addDataDeps(ruleContext)
	.build());

The comment says "also visit its data as data", but then only visits its data as data, ignoring the runfiles of srcs. I don't think it's correct for a data edge to merge strictly fewer runfiles than a non-data edge. I can send a fix so that we know how much this would break.

@comius Are there any thoughts on Starlarkifying filegroup to make its exact semantics more obvious?

[fmeum]

#25365 fixes this particular issue, but changing filegroup logic that has been unchanged since at least 2015 is scary.

CC @lberki