Friction: Using bazel with skaffold

As discussed in office hours, this is a documentation of a point of friction using both skaffold and bazel.

Skaffold expects to find its inputs in the filesystem, whether that's skaffold.yaml itself, kustomization files, or kubernetes resource yaml files.

A Bazel user expects to be able to generate any file on demand with a bazel build command, with explicit dependencies and sandboxing. The typical bazel pattern is to avoid putting generated files into the source tree.

A workaround is to have something like `bazel run` commands to generate files, then invoke skaffold over those. It works but it's friction.

Skaffold could potentially have greater awareness of inputs being generated on-demand by bazel.