Fix Cypress tests and add them to Travis.

[willrlin]

Issue

Addresses #171

Description

Fix the Cypress tests and add them to the Travis config.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Prototype/POC (not to merge)
• This change is a refactor/address technical debt
• This change requires a documentation update
• This change requires a SQL Script

How Can This Be Tested/Reviewed?

Run cypress tests with yarn test:apps.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have updated the changelog to include a description of my changes

[anders-schneider]

LGTM! Two questions below, but not blocking

[willrlin]

Only one portion of the member.spec.ts test is flaky (passes on one branch and locally, but not the pull request branch), so I'm going to disable just that part in the interest of getting all the rest of these running on presubmit. It also seems likely that we may want to delete some of those tests anyway once we remove applications.