Fix Tracking & 404 Banner

[gantoreno]

Fixes GRO-460, GRO-472

• Uses the shared chrome as the nav elements in the 404 page instead of the legacy ones.
• Sets build env to production for amplify deployments to enable anonymous tracking
• Adds the shared-chrome to the committed file list so that it stays up-to-date with master.

[iethree]

Instead of manually pulling the chrome in a PR, can this just be part of the build process for this repo? isn't that the whole point of shared chrome? so we don't have to sync code? it should just get pulled in from the single source of truth at build time.

[gantoreno]

@iethree it is a part of the build process (see script/build). The pulling of the latest chrome was something I did very early and I thought that it would eventually be overridden by whatever the repo auto-pulled from CI eventually. It was also based on the wrong assumption that the issue was the script (turns out it was the second commit about using the actual chrome that fixed it).

Strangely enough, now that you pointed it out (and I see that the chrome is still part of the diff and not up-to-date or behind), I realized that the issue isn't pulling it on build, but that it's not being committed, so it just stays hanging as a dirty file in CI that never gets updated.

Just pushed fix: also commit shared chrome which adds _data/shared-chrome.json to the committed files - I didn't know that _data was not part of the auto-updated/committed files. That should fix it.

I also updated the PR description.