(#490) Add an automated production sanity test

[rwood-moz]

This PR adds a production sanity E2E test which verifies the splashscreen appears, and we are able to sign-in to Appointment production. The suite can be run on your local machine against locally-installed browsers or against browsers located in the BrowserStack Automate cloud platform.

For more details please see the included /test/e2e/README file. If you want to try running the tests in BrowserStack and don't have a BrowserStack account yet let me know and I can get you set up :)

[MelissaAutumn]

Changes looks good, I've got some comments but nothing blocking (stuff can be moved to another issue.)

One question though, it seems like you're building a second project within frontend. Should we consolidate it with frontend's package.json and use a env.test (with env.test.example for the repo) and dev dependencies?

I'm okay with two projects if that's easier to manage, but we'll need to make sure ides still detect the linting rules and such okay.

[devmount]

Great work, @rwood-moz! Thank you!

[rwood-moz]

Changes looks good, I've got some comments but nothing blocking (stuff can be moved to another issue.)

One question though, it seems like you're building a second project within frontend. Should we consolidate it with frontend's package.json and use a env.test (with env.test.example for the repo) and dev dependencies?

I'm okay with two projects if that's easier to manage, but we'll need to make sure ides still detect the linting rules and such okay.

Thanks for your feedback Mel, appreciated! I prefer to keep the E2E tests in their own project because they are testing the entire application and need both the frontend and backend to be running; so I created the new test/e2e folder at the root level not under the frontend or backend folders - I hope that's ok!

[MelissaAutumn]

Changes looks good, I've got some comments but nothing blocking (stuff can be moved to another issue.)
One question though, it seems like you're building a second project within frontend. Should we consolidate it with frontend's package.json and use a env.test (with env.test.example for the repo) and dev dependencies?
I'm okay with two projects if that's easier to manage, but we'll need to make sure ides still detect the linting rules and such okay.

Thanks for your feedback Mel, appreciated! I prefer to keep the E2E tests in their own project because they are testing the entire application and need both the frontend and backend to be running; so I created the new test/e2e folder at the root level not under the frontend or backend folders - I hope that's ok!

Yep root level is okay, I just missed that. I thought it was under frontend. That works for me!