Fix type import ordering

[rsslldnphy]

it looks like #153 introduced a bug whereby import type ... imports would no longer be sorted with their matching group even if a type-specific group was not present. (see #329 for more details). this pr changes the matching logic such that:

• non-type imports go in the first matching group if there is one
• type imports go in the first matching type-specific group if there is one, or the first matching non-type-specific group if there is one
• otherwise the behaviour remains unchanged, they go in the THIRD_PARTY_TYPES_SPECIAL_WORD or THIRD_PARTY_MODULES_SPECIAL_WORD groups depending on the node type and whether the THIRD_PARTY_TYPES_SPECIAL_WORD exists in the config.

as this behaviour is starting to feel a little complex i've added a comment in the code - i see there's not a ton of comments so happy to take it out if it's against house style. i also don't love the code so refactoring suggestions welcomed.

this fixes #329 - i've tested it on my codebase and the incorrect ordering changes introduced by 5.0.0 were reversed.

[byara]

Looks good @rsslldnphy and thank you for fixing this bug! Could you please add some snapshot tests for this case? After that, I'll merge this and we can release the fixes.

[rsslldnphy]

Sure thing, have done! Thanks :-)

[rsslldnphy]

hmm not sure why it's failing yarn --immutable with a 404 - works locally. maybe worth rerunning?