Migrate site deployment to Firebase

[critzo]

This PR replaces the Travis deployment to AWS with deployment to Google Firebase. Only the production site is added to this PR in the in the interest of moving off AWS completely. All changes in this PR can be previewed here: https://mlab-speedtest.firebaseapp.com

All currently completed translations from Transifex are also added with this PR. Supported languages other than English will now include:

• az - Azerbaijani
• zh - Chinese
• nl - Dutch
• fr - French
• de - German
• el - Greek
• hi - Hindi
• id - Indonesian
• fa - Persian
• ru - Russian
• es - Spanish

@nkinkade PTAL?

---

This change is 

[nkinkade]

Once comment on the .travis.yml file, and a general question about whether we should be including any "lock" and "cache" files in the repo. For example, the yarn.lock file says it is autogenerated (and it's very large). Is this a file that needs to be in version control?

Reviewed 39 of 43 files at r1.
Reviewable status: 1 change requests, 0 of 1 approvals obtained (waiting on @critzo and @nkinkade)

---

.travis.yml, line 17 at r1 (raw file):

  on:
    repo: m-lab/mlab-speedtest
    all_branches: true

I think all_branches can be removed, since we are dealing with tag here, not a branch.

---

yarn.lock, line 1 at r1 (raw file):

# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.

Should this auto-generated files be included in version control?

[critzo]

I'll have to test without the yarn file in the repo. I think we can get away with dropping it but will check. It's only there to get around some issues with bower being deprecated. The reality is that this app needs a major update but getting it migrated off AWS will have to precede that since we likely won't get to that for a bit. I'll make another commit and ping you back. Thanks @nkinkade

[nkinkade]

How is yarn.lock generated? Is package-lock.json generated too?

Reviewed 1 of 3 files at r2.
Reviewable status: 1 change requests, 0 of 1 approvals obtained (waiting on @critzo)

[nkinkade]

Reviewable status: 1 change requests, 0 of 1 approvals obtained (waiting on @critzo)

---

.travis.yml, line 17 at r1 (raw file):

Previously, nkinkade wrote…

I think all_branches can be removed, since we are dealing with tag here, not a branch.

condition can be removed too.

[critzo]

@nkinkade The app is dated enough that it is using bower to package node modules. It needs to be updated in the future after it is migrated. Just to get the app updated and working, it was necessary to do an initial migration step, as described here. yarn.lock was generated when I used the bower-away node module to repackage and update the node modules in the app. bower-away uses yarn and generates that file, and I assume package-lock.json as well.

I would recommend that we get this app hosting migrated and deal with refactoring it later. Is that ok? Realistically, we need to use something like webpack and that will take more time.

[critzo]

---

.travis.yml, line 17 at r1 (raw file):

Previously, nkinkade wrote…

condition can be removed too.

removed in most recent commit.

[critzo]

---

yarn.lock, line 1 at r1 (raw file):

Previously, nkinkade wrote…

Should this auto-generated files be included in version control?

This file does need to be in version control

[nkinkade]

@critzo: Thanks for looking into all these. LGTM!

Reviewed 2 of 43 files at r1, 1 of 1 files at r3.
Reviewable status: complete! 1 of 1 approvals obtained (waiting on @nkinkade)