feat: add support for import-alias-naming rule

[denisvmedia]

Closes #880.

[denisvmedia]

@chavacava I'm thinking of making it an array of rules instead of a single rule. This will let users submitting multiple regexes that will be combined as logical AND (so that every rule must match). What do you think?

upd: to be clear, the idea is clarity of the configuration. The first regex can be the main, positive, match. Other subsequent regexes may be used to imply negative matches. E.g. to exclude v1 the user will provide a negative match ^(?!v1$).*. However, it is possible to do in a single regex, the readability will suffer, I'm afraid.

[chavacava]

@chavacava I'm thinking of making it an array of rules instead of a single rule. This will let users submitting multiple regexes that will be combined as logical AND (so that every rule must match). What do you think? upd: to be clear, the idea is clarity of the configuration. The first regex can be the main, positive, match. Other subsequent regexes may be used to imply negative matches. E.g. to exclude v1 the user will provide a negative match ^(?!v1$).*. However, it is possible to do in a single regex, the readability will suffer, I'm afraid.

I personally prefer a single argument. That way there is no need to explain (and understand) how multiple regex are combined (AND or OR?). Yes it can lead to a complex regex but... if you are playing with a regex you know what are you doing :)

[denisvmedia]

I personally prefer a single argument. That way there is no need to explain (and understand) how multiple regex are combined (AND or OR?). Yes it can lead to a complex regex but... if you are playing with a regex you know what are you doing :)

OK, let it be a single regex.