* docs(testing): add example on how to use ts path aliases within jest global setup/teardown
Jest global setup/teardown scripts run before path aliaes are mapped, so the path resigstration must
happen in the userland global scripts that are set to run
initially the thought of doing this within
the jest executor was thought, but this will provide an inconsistent way to running tests if the
tests are run via an editor plugin or calling `jest` directly; therefore, it's deferred to register
the paths within userland files that are needing the paths to be registered in order to allow for
proper handling (cleanup) and not to overcall unneeded features when global scripts are not in use
for those not using the feature.
ISSUES CLOSED: #8709
* cleanup(testing): test the usage of jest global scripts to ensure no regressions
streamline e2e jest project testing and update global tests to test global functions are working as
intended
