Who would expect the browser user-agent to actually call itself "EDG" and not "EDGE" though? If you edit the user-agent to include "EDGE" in place of "EDG" everything works, someone thought "EDG" was surely a typo. Malice and stupidity and all that.
Now why they're still sniffing user agents instead of doing feature detection is a good question for Google, who themselves, to the best of my knowledge, push for feature detection instead of sniffing user agents as best practice. Do as we say - not as we do?
In some cases feature detection is not enough because while the browser may define the method you need it’s implementation is broken. A good example of this was indexeddb was horribly broken in safari and even doing feature detection was tricky so you had to check the user agent to see that it probably had a bad indexeddb and work around it. It’s never ideal and there is always possibly and more clever work around but sometimes you have a tight timeline and need a site to work in a specific browser.
Google is not a single entity. Chrome DevRel and Docs web front end are not even remotely related teams, and DevRel cannot dictate practices to other teams.
Now why they're still sniffing user agents instead of doing feature detection is a good question for Google, who themselves, to the best of my knowledge, push for feature detection instead of sniffing user agents as best practice. Do as we say - not as we do?