[unpacked-dimensions-range-ordering] - configuration

[sconwayaus]

Summary
Lint rule [unpacked-dimensions-range-ordering] enforcing scalar ranges [N] for zero based unpacked arrays goes against the grain of my companies internal style guide for synthesisable code.

Proposal
Ideally I'd like to add configuration to the rule so it is more flexible, and retain the current default behaviour.

I propose adding 4x boolean configuration parameters

allow_range_big_endian: true
allow_range_little_endian: false
allow_scalar: true
range_big_endian_prefer_scalar: true // ignored if allow_big_endian or allow_scalar are false