Fix false negatives in prefer-result-array-groups rule

[ota-meshi]

fixes #355

This PR makes fix some false negatives and improves autofix.

I fixed the false negatives of the source code written in TypeScript.

const match = /(?<foo>foo)/u.exec(str)!
match[1]; // <-

const match2 = /(?<bar>bar)/u.exec(str) as RegExpExecArray
match2[1] // <-

I modified it to handle the TSNonNullExpression and TSAsExpression nodes contained in these codes.

I also found that there were false negatives when using conditional statements, so I fixed these as well.

const match = /(?<foo>foo)/u.exec(str)
if (match) {
    match[1] // <-
}

const match2 = /(?<bar>bar)/u.exec(str)
match2
    ? match2[1] // <-
    : null;

const match3 = /(?<baz>baz)/u.exec(str)
match3 && match3[1] // <-

const match4 = /(?<qux>qux)/u.exec(str)
if (!match4) {
} else {
    match4[1] // <-
}

Finally, fix the problem that the code written in TypeScript cannot be autofixed.

const match = /(?<foo>foo)/u.exec(str)
match?.[1]

This was a problem because the match variable was of type (RegExpExecArray | null), which stopped autofix.
I changed it to autofix even for type (RegExpExecArray | null).

[RunDevelopment]

Awesome work! LGTM;

Feel free to merge this at any time. I leave it at your discretion whether this is to be included in the patch for #354.

[ota-meshi]

ESLint's Semantic Versioning Policy does not seem to include more reporting fixes in patch releases.
So, I will not include this change in the patch according to it policy.
https://github.com/eslint/eslint#semantic-versioning-policy