split up chrome tests (#19209)
Starts #18502
### Summary of the issue:
Our system test bottle neck is chrome tests. There are too many chrome
tests. They take up 20 min off time which could be parallelized down to
3-5min chunks
### Description of user facing changes:
None
### Description of developer facing changes:
Reduced PR times, better grouping logic when adding to
chromeTests.robot.
Symbols tests are now the longest tests (6min). That means 14min from
builds is shaved off from this PR.
Builds have gone from 40-45min to 30min on average.
### Description of development approach:
Added tags to group chrome tests into sub groups.
This is to establish grounds for a potential refactor in the future.
Added timeout constraints to the 3 bottlenecks of the build: building
NVDA source, building the launcher and system tests.
This is so we can monitor and constrain build time lengths.
With these constraints, we guarantee a 40min or faster build.
### Testing strategy:
GitHub actions runners
### Known issues with pull request:
This doesn't refactor the test files fully, just begins the proposal for
logical groupings.
Further work is suggested to refactor chromeTests.py/chromeTests.robot
