Type-only auto-import improvements

[andrewbranch]

Closes #53008

1. When more than one import declaration from the same module specifier exists, find the one that’s the best match with respect to type-onlyness instead of modifying the first one to work:

   import type {} from "react"; // <-- auto-imported types will go here
   import {} from "react";      // <-- auto-imported values will go here

2. When promoting a type-only import declaration to a real one due to a new value import, always add type modifiers to the existing specifiers, even if emit settings don’t require it. For example, if a value import of SomeValue is to be auto-imported here:

   import type { SomeType } from "mod";

   the result will now always be:

   import { SomeValue, type SomeType } from "mod";

   regardless of compiler options. Previously, we would only insert the type modifier on SomeType if it was necessary according to compiler options, e.g. if verbatimModuleSyntax is enabled.