Hybrid install

Now that rules_nodejs 0.16.8 supports installing Bazel workspaces out of npm packages, rules_typescript uses this mechanism.

BREAKING CHANGES

• We no longer recommend fetching rules_typescript at all. Instead, just include an npm dependency on @bazel/typescript and/or @bazel/karma and call the installer with

  load("@npm//:install_bazel_dependencies.bzl", "install_bazel_dependencies")
  install_bazel_dependencies()
  

  after your yarn_install or npm_install is done. See the updated README.md.
• Karma rules (ts_web_test, ts_web_test_suite) are now loaded from @build_bazel_rules_karma workspace rather than @build_bazel_rules_typescript

Other updates

• You no longer need to install any Go-related rules. All our Go programs are now distributed as pre-compiled binaries for each of the three major platforms.
• Karma stack traces are cleaned up, see #369
• The rules_typescript_dependencies function is deprecated. You can remove usage of it.
• New rules karma_web_test and karma_web_test_suite which allow you to pass a karma.conf.js. These are needed for testing on Saucelabs. We don't have API docs for these yet, because our doc publishing is affected by refactoring (we expect these will move to rules_nodejs for the next release). See usage in examples/testing
• Our Go-based devserver binary runs on Windows, but we are still making fixes to the rules to work on Windows.
• The tsc_wrapped binary is getting a special hook to run Angular's new ngtsc compiler
• We no longer depend on a fork of the Karma project. Changes needed for ibazel were released in Karma 4.0.0
• Performance improvement to our static analyzer, http://tsetse.info