Ensure dist-newstyle directories are ignored everywhere.

@tclem ran into an issue where he had built `semantic-source` from the
`semantic-source` directory; `cabal` placed a `dist-newstyle`
directory there, which was fouling up Bazel due to the fact that
`cabal` generates binary files called `BUILD`, and Bazel tries to
interpret these files as package configurations. Not good!

We can't use a glob here because .bazelignore files don't support
globbing (bazelbuild/bazel#7093), so it
suffices to ignore all the projects' `dist-newstyle` directories so
that no one runs into this again.

.bazelignore

@@ -1,2 +1,19 @@
+semantic/dist-newstyle
+semantic-analysis/dist-newstyle
+semantic-ast/dist-newstyle
+semantic-codeql/dist-newstyle
+semantic-core/dist-newstyle
+semantic-go/dist-newstyle
+semantic-java/dist-newstyle
+semantic-json/dist-newstyle
+semantic-parse/dist-newstyle
+semantic-proto/dist-newstyle
+semantic-python/dist-newstyle
+semantic-ruby/dist-newstyle
+semantic-scope-graph/dist-newstyle
+semantic-source/dist-newstyle
+semantic-tags/dist-newstyle
+semantic-tsx/dist-newstyle
+semantic-typescript/dist-newstyle
 dist-newstyle
 tmp