Editor resolver: untyped `editorGroupFinder#findGroup` causes issues

We are currently calling `editorGroupFinder.findGroup` with untyped inputs, but this is problematic: because some of the logic within requires the editor type to be known to do proper `matches` and `contains` checks. Since the untyped editor doesn't know the `override` before being resolved, I had to add the following ugly workaround: https://github.com/microsoft/vscode/blob/e4ac631e9dbf0aa93a4371c4f5f3b8dc43422afb/src/vs/workbench/services/editor/common/editorGroupFinder.ts#L205-L205 I would hope that we could possibly stop calling `findGroup` with untyped inputs to address this? How is the group being used in the resolver service given it resolves it again with the typed editor?