Add preserve_symlinks attr into bazel rules

Fix bug in jazelle script

noticed a discrepancy between:
1. `yarn foo 'hello world'` and
2. `jazelle foo 'hello world'`

In the former case, `'hello world'` is treated as a single arg (as it should, since it's single quoted). But in the latter case jazelle is not correctly treating the quoted argument as a single argument because of word splitting.

The fix is to use `"$@"` instead of `$@` in the underlying bazel rule that invokes node.

Fix missing html attributes in SSR

Fixes https://jeng.uberinternal.com/browse/WPT-5493

We had a test for this, but the test fixture was not correct

Co-authored-by: Ryan Tsao <ryan.j.tsao@gmail.com>

Use system bazel if it exists and is the right version

CI systems might want to preinstall bazel (e.g. in a docker layer etc), so allow jazelle to pick up a preinstalled bazel binary if one already exists, rather than attempting to download again

Add type helper for extracting deps types

This type helper can be useful to get the types of resolved dependencies objects from the declared types based on tokens.

Update flowtype for prepared (fusionjs#721)

fusionjs#721

`sideEffect` doesn't actually need to return a Promise since it is wrapped once in Promise.resolve and the other two times the return type is discarded.

Throw when lockfiles are out of date

Refactor installation to use stashing strategy

Refactor installation to use stashing strategy:

- when installing A, install it into A's stash, then move A's node_modules up to top level
- when installing B, stash A's node_modules into A's stash, install into B's stash, then move B's node_modules up to top level
- from then on, unstash whichever one is requested by a `jazelle install` call

This strategy optimizes for fast context-switching between projects, assuming no yarn.lock changes between switches

Previously the installation strategy attempted to reuse the existing node_modules regardless of what was in it, but that approach turned out to create cases where the wrong version of things would be installed after context-switching between projects with different (but compatible) dep versions. This change isolates node_modules per project so that there's never cross-contamination

This should avoid the need of running `jazelle prune` when context-switching

Upgrade to Flow 0.109.0

Upgrades all packages and scaffolds to utilize Flow 0.109.0.

No major issues requiring code changes were found while doing this upgrade other than making sure that all dependencies to Styletron were locked to a revision higher than the stated ones in this publish: styletron/styletron@dcf40cf

(such as the legacy website scaffold)

Do flag all projects as changed if WORKSPACE file changes

Previously, if the input to `jazelle changes` only listed the WORKSPACE file, no changes would be reported. Instead, the command should report that all projects have changed. This PR fixes that