When running the Cypress tests from landing-page-frontend, they only appear to work if executed against the local dev proxy via "npm start" (e.g. stage.foo.redhat.com). These should also work against stage and prod directly, otherwise their usefulness as e2e tests diminishes.

Goals
Identify the cases where tests fail if we run directly against stage environment or prod; tests need to be environment agnostic. If we can identify any "baked-in" assumptions that prevent the tests from working, we can address those and fix them.

Steps to Reproduce

1. Do the needful (clone the landing-page-frontend repo, npm install, etc)
2. Do not start the proxy locally
3. In cypress config, set the URL to console.stage.redhat.com
4. Before running cypress tests, set the HTTP_PROXY env var 
   1. e.g. export HTTP_PROXY=http://squid.corp.redhat.com:3128
5. Run cypress tests, observe the failures happening

Example config snippet (add to cypress config to easily execute against stage): https://gist.github.com/catastrophe-brandon/abe8642f54a548ff1906fb381623322d