[e2e] Update tests to be compatible with viper

[unlikelyzero]

Summary

We'll need to update our test suite to be backwards compatible with VIPER execution. This is a running list:

• Update all path in await page.goto to include a ./ instead of /
• Update directory structure such that all fixture files resolve to the same root directory
• Update all references to the name of the Shared Items folder and My Items. We should probably save directly to folder under My Items. Need to check with @jvigliotta and @davetsay and @akhenry to understand how prevalent this might be.
• Update tests to navigate by URL to a domain object created in a common function like 'getOrReplace' which returns the object's uuid. Another pattern is create object with ObjectName_UUID e.g. 'Unnamed Condition Set' becomes 'ConditionSet_asdkfn_asdfnsk_' or 'ConditionSet_timestamp'. Best effort (~2 hours) Scope out for now
• Parameterize tests so that they can use real telemetry sources or example telemetry. Create or update any associated helper functions based on the above. Start with a single test (good candidate here) as POC and example (Best effort (~2 hours)
• Set default folder location for objects into common folder - Broken out into separate issue.
• Include uuid and testcase info within name of object created by appActions

[loftwah]

I've raised a PR for this one but it looks like there are more possible changes. I am able to have a look at anything else when they come up. I hope I have read everything correctly, it would be an honour to contribute to NASA.

[unlikelyzero]

@loftwah thanks for taking this one on! It's going to grow quite spectacularly, but that was definitely the most important step. If you don't mind, would you mind moving to the Discussion board to talk about taking on another testing task?

I just stumbled upon #3213 (comment)