Documentation/dev/build: "tectonic-installer" -> "installer"

[wking]

Catching up with e22e31f (coreos/tectonic-installer#3142). Running bazel build tarball on master actually gets you a tectonic-dev.tar.gz with a root tectonic-dev directory, but I've left that alone for now (maybe it depends on environment variables like cutting releases?). The tarball I built also lacks the darwin/linux subdirectories:

$ tree tectonic-dev/installer/
tectonic-dev/installer/
├── tectonic
└── terraform

But by stopping at the installer directory I don't have to worry about figuring out how cross-platform builds work now ;).

Fixes #33.

[yifan-gu]

/lgtm
/ok-to-test

[yifan-gu]

/ok-to-test

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[wking]

Rebased to get a new hash for Prow to avoid:

* aws_iam_role.etcd_role: Error creating IAM Role ci-op-2n8ifypw-68485-etcd-role: EntityAlreadyExists: Role with name ci-op-2n8ifypw-68485-etcd-role already exists.
    status code: 409, request id: 5f180a1f-8c60-11e8-9bb4-133f5ea804b8

in the batch-merge job. Hopefully that unsticks the tide merge pool, but it means this PR needs a fresh LGTM. @yifan-gu?

[wking]

This time the e2e-aws errors were:

3 error(s) occurred:

* module.vpc.aws_route_table_association.worker_routing[5]: index 5 out of range for list aws_route_table.private_routes.*.id (max 5) in:

${aws_route_table.private_routes.*.id[count.index]}
* module.vpc.data.aws_route_table.worker[5]: data.aws_route_table.worker.5: Your query returned no results. Please change your search criteria and try again.
* module.vpc.aws_route.to_nat_gw[5]: index 5 out of range for list aws_route_table.private_routes.*.id (max 5) in:

${aws_route_table.private_routes.*.id[count.index]}

[yifan-gu]

retest

[wking]

retest

@yifan-gu, I think you meant /retest?

[yifan-gu]

/retest

[wking]

This time the e2e-aws error was an interrupt signal:

2018/07/24 22:00:00 Container test in pod e2e-aws completed successfully
{"component":"entrypoint","level":"error","msg":"Entrypoint received interrupt: terminated","time":"2018-07-24T22:05:45Z"}
2018/07/24 22:05:45 error: Process interrupted with signal interrupt, exiting in 2s ...
2018/07/24 22:05:45 cleanup: Deleting template e2e-aws

[yifan-gu]

/retest

[wking]

This time the e2e-aws error was:

* aws_launch_configuration.worker_conf: Error creating launch configuration: AlreadyExists: Launch Configuration by this name already exists - A launch configuration already exists with the name ci-op-nj8csswq-68485-worker-20180725185159419400000001
	status code: 400, request id: d44dd17f-903b-11e8-bad1-dd6846aecb37

/retest

[wking]

This time the e2e-aws errors were:

3 error(s) occurred:

* module.vpc.aws_eip.nat_eip[0]: 1 error(s) occurred:

* aws_eip.nat_eip.0: Error creating EIP: AddressLimitExceeded: The maximum number of addresses has been reached.
	status code: 400, request id: 32c29992-2ad5-40e8-b0e5-524c22493368
* module.vpc.aws_eip.nat_eip[4]: 1 error(s) occurred:

* aws_eip.nat_eip.4: Error creating EIP: AddressLimitExceeded: The maximum number of addresses has been reached.
	status code: 400, request id: ab2739f6-d17f-4747-81e7-6643d31005d8
* module.vpc.aws_eip.nat_eip[1]: 1 error(s) occurred:

* aws_eip.nat_eip.1: Error creating EIP: AddressLimitExceeded: The maximum number of addresses has been reached.
	status code: 400, request id: d62268c1-6d36-4604-aaaf-eabd7b2e5fc7

/retest