Feature/setup cypress for e2e testing

[barneyjeffries]

Description of the Change

This PR adds Cypress for e2e testing, configured and with 2 tests set-up:

1. settings.test - the test adds the admin credentials for a test azure account and uploads a file to verify integration is working
2. admin.test - the test logs in and deactivates and activates the plugin

NOTE: We need to add the test azure account credentials to the GitHub repo but I don't have permissions to do this. The constants should be set as:
MICROSOFT_AZURE_ACCOUNT_NAME
MICROSOFT_AZURE_ACCOUNT_KEY
MICROSOFT_AZURE_CONTAINER

Closes #154

How to test the Change

1. Pull changes
2. Run npm install
3. Build assets: npm run build
4. Start local environment: npm run env:start
5. Open Cypress for testing supplying test credentials:
   CYPRESS_MICROSOFT_AZURE_ACCOUNT_NAME=[accountname] CYPRESS_MICROSOFT_AZURE_ACCOUNT_KEY=[key] CYPRESS_MICROSOFT_AZURE_CONTAINER=[container] npm run cypress:open
6. Use Cypress GUI to run tests and verify they are working

Changelog Entry

Added - New feature

Credits

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.

[iamdharmesh]

@barneyjeffries Thanks a lot for the PR.

@jeffpaul could you please help with adding Azure credentials to GH action secrets to the repo? I tried running tests locally and it seems working fine.

Thanks.

[jeffpaul]

@iamdharmesh I've added what I believe are the necessary secrets, but please let me know if anything isn't acting as expected and I'll research further... thanks!

[jeffpaul]

@iamdharmesh bumping this back up to see if the repo secrets allow this to function as you'd expect?

[iamdharmesh]

@jeffpaul Thanks for adding repo secrets. it's working fine after some minor yml file changes.

[iamdharmesh]

Thanks @barneyjeffries, LGTM 🚀