Consolidate e2e Repro Specs

[iethree]

There is significant (4-6 second) setup overhead in separate test files in CI. combining dozens of reproduction specs that all have 1 or 2 tests, provides several minutes of CI savings in many cases

We should consolidate all of these, even when there are only a couple offenders to eliminate the pattern from the codebase and to keep it from continuing.

Tasks

Beta Give feedback

1. Combine Filters Reproduction into new e2e job #43328
   .CI & Tests .Team/AdminWebapp no-backport +3
   
2. Combine models repro specs #43342
   .CI & Tests .Team/AdminWebapp no-backport +3
   
3. Combine question e2e reproductions into fewer specs in a different job #43271
   .CI & Tests .Team/AdminWebapp no-backport +3
   
4. Combine tabular viz e2e specs #43519
   .CI & Tests .Team/AdminWebapp no-backport +3
   
5. Consolidate chart viz e2e specs #43619
   .CI & Tests .Team/AdminWebapp no-backport +3
   
6. Consolidate sharing e2e specs #43514
   .CI & Tests .Team/AdminWebapp no-backport +3
   
7. Combine e2e native filter specs #43527
   .CI & Tests .Team/AdminWebapp no-backport +3
   
8. Consolidate permissions e2e specs #43552
   .CI & Tests .Team/AdminWebapp no-backport +3
   
9. Consolidate custom column e2e specs #43616
   .Team/AdminWebapp no-backport +2
   
10. Consolidate dashboard e2e specs #43613
    .CI & Tests no-backport +2
    
11. Consolidate joins specs #43717
    .Team/DevEx no-backport +2
    
12. Consolidate dashboard-card specs #43716
    .CI & Tests .Team/DevEx no-backport +3
    
13. Combine search e2e specs #43718
    .CI & Tests .Team/DevEx no-backport +3
    
14. Combine native e2e specs #43844
    .Team/DevEx no-backport +2
    
15. Combine embedding e2e specs #43843
    .Team/DevEx no-backport +2
    
16. Combine collections e2e specs #43841
    .Team/DevEx no-backport +2
    
17. Combine actions e2e specs #43846
    .CI & Tests .Team/DevEx backport +3
    
18. Combine and reorganize admin e2e specs #43853
    .CI & Tests .Team/DevEx no-backport +3
    
19. onboarding
20. binning

[iethree]

One down side to this project is that some developers find working with large files to be rather cumbersome.

One alternative approach suggested by @romeovs is keeping test files small, but running them via imports into larger files, which should solve the performance problem.

see discussion and proof of concept PR:

• POC: import specs instead of creating one big spec file #44889

One open question:

• Do most developers find large files hard to work with?

One blocker:

• we need a linter that can ensure that all spec files are imported into runner files so that we don't end up with orphan spec files that never get run.