Refactor generate engine manifest to accept blacklist as an argument.

blimp/docs/container.md

 # Running the engine in a Docker container
 
 For local development and testing, you can run the engine in a Docker
 container.
 
 The steps are:
 
 1. Bundle the engine and its dependencies.
 
 1. Build a Docker image.
@@ skipping 21 matching lines @@
 ## Bundle Engine
 
 The `blimp/engine:blimp_engine_bundle` build target will bundle the engine and
 its dependencies into a tarfile, which can be used to build a Docker image.
 This target is always built as part of the top-level `blimp/blimp` meta-target.
 
 ### Update Engine Dependencies
 
 `blimp/engine/engine-manifest.txt` is a list of the engine's runtime
 dependencies. From time to time, this list may need to be updated. Use
-`blimp/tools/generate-engine-manifest.py` to (re)generate the manifest:
+`blimp/tools/generate-manifest.py` to (re)generate the manifest:
 
 ```bash
-./blimp/tools/generate-engine-manifest.py \
+./blimp/tools/generate-manifest.py \
     --build-dir out-linux/Debug \
     --target //blimp/engine \
-    --output blimp/engine/engine-manifest.txt
+    --output blimp/engine/engine-manifest.txt \
+    --blacklist blimp/tools/manifest-blacklist.txt
 ```
 
 Be sure to review the generated manifest and remove any false runtime
 dependencies.
 
 For all entries listed in the manifest that are not from
 `//third_party/blimp_fonts`, ensure that the target that generate that artifact
 is manually listed as a dependency of `//blimp/engine:blimp_engine_bundle` to
 ensure that it is built before the bundle step happens.
 
@@ skipping 34 matching lines @@
 ```bash
 docker run -v $CONFIG_DIR:/engine/data -p 443:25466 blimp_engine
 ```
 You can also pass additional flags:
 
 ```bash
 docker run ... blimp_engine --with-my-flags
 ```
 See the [blimp engine `Dockerfile`](../engine/Dockerfile) to find out what flags
 are passed by default.