Restore IE Mode e2e testing in Windows

[Jaifroid]

Fixes #1088. This test got accidentally removed in a recent PR. Please see explanation in #1088 as to why I don't believe it's worth running Chrome (as opposed to Edge) tests specifically in the Windows VM. Testing is already quite slow, so we should focus on tests that clearly add value.

[Rishabhg71]

@Jaifroid, I like your idea of removing the Chrome Windows Tests, as all tests were taking around 8 minutes to complete. Continuing this discussion, I believe there's an opportunity to explore an even more effective solution. Currently, the tests are categorized by OS. Perhaps, we could consider a different categorization approach. Presently, Windows tests involve about 3 to 4 steps, whereas Linux tests encompass around 10 to 12 steps. Let's brainstorm for potential improvements.

[Jaifroid]

Great, thank you! The main aim here was to reintroduce the IE11 test (IE Mode), and so as not to extend the Windows tests even more, it seemed best to remove the Chrome test which is really redundant on Windows if we are also testing in Edge. I agree we should look for ways of making tests more efficient if possible. They run significantly faster on Linux than on Windows (I suspect because the Windows VMs on GitHub just don't have so many runners), but we do need some Windows testing. I'll merge now.