aamtests (EdgeDriver): Compute correct pid & Enable running IA2 tests - #60733

@yezhizhen Thanks for putting this together! I actually opened a very similar PR a few days ago (#60811).

Looking at your implementation, I noticed a few differences in how we approached this. In hindsight, my approach for a couple of these was a bit over-engineered, but the first point might still be worth considering:

1. I returned "edge" as the product_name instead of "MicrosoftEdge". "edge" seems to be what was used across most of the codebase, so using it here might help prevent issues down the line. And since it's mostly checked if that product_name in window name etc.
2. I handled both"MicrosoftEdge" and "edge". After testing, I realized these extra checks weren't actually necessary as it consistently gets MicrosoftEdge from the webdriver, so your approach here is totally fine.
3. I initially checked for an ms:processId key, expecting it given the other ones before debugging and realizing it only had a goog:processId. Anyway, making my extra checks isn't needed, I left it in incase it case as it seemed strange and figured it might change overtime... but your approach is simpler, and less over-engineered.

Overall, your changes look great to me! Aside from the supernitty #1, of potentially updating the returned product name to "edge" for consistency. I will actually abandon my change to keep things simple, so it doesn't conflict with this in any way, since they functionally do the same thing.

@Ms2ger, can you merge this one? The Safari failure is unrelated.

edit: nevermind, I could merge this one for whatever reason!