feat: no-regex-spaces support v flag

[ota-meshi]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[X] Changes an existing rule (template)

What changes did you make? (Give an overview)

Refs #17223

This PR modifies the no-regex-space rule and adds support for regexp v flag.

Is there anything you'd like reviewers to focus on?

[netlify]

✅ Deploy Preview for docs-eslint ready!

Name	Link
🔨 Latest commit	28ca7f4
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/64bfb013037520000859e6a4
😎 Deploy Preview	https://deploy-preview-17407--docs-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mdjermanovic]

Parsing with the v flag is significantly different, so the assumption that unknown flags don't include v could be problematic. For example, these patterns are parsable without the v flag, but the consecutive spaces don't end up being in character classes and are therefore reported (and even autofixed in the first case):

/* eslint no-regex-spaces: "error" */

function createRegexes(additionalFlags = "") {
    const flags = `${additionalFlags}v`;
    return [
        new RegExp("[[abc]  ]", flags), // false positive, autofixed to "[[abc] {2}]"
        new RegExp("[[abc]\\q{  }]", flags) // another false positive
    ]
}

I'm not sure if there is a good solution aside from ignoring RegExp constructor calls for which the flags cannot be determined.

[ota-meshi]

Thank you for letting me know about that problem!
I changed this PR to ignore the check if the flag cannot be determined.

[nzakas]

LGTM. Would like @mdjermanovic to verify before merging.

[mdjermanovic]

LGTM, thanks!