feat: add scope for dependency rules

[mohanraj-r]

Instead of having the same check expressed with different names for the different scopes (prod, dev etc), it would be good to have a rule specify scope(s).

e.g.

'no-absolute-version-dependencies': ['prod', 'dev'],
'prefer-alphabetical-dependencies': ['peer', 'optional']

[justnewbee]

makes great sense, but the format might be like `xx: ['error', scope?]', where scope default is all