Rspec.Aliases in root-level config

[sl4vr]

Rspec.Aliases in root-level config

Pros

• No need to change anything but RuboCop::RSpec::Language module
• Should be faster then dynamic matchers since it fully uses of AST matchers

Cons

On the other hand it's pretty inconsistent:

• Bottom-level configuration for aliases will be ignored in most cases
• In some rare cases root-level aliases can be ignored. E.g. if project doesn't use bundler and we run rubocop from some bottom-level directory which already has its own .rubocop.yml without Rspec.Aliases. But still no one gonna do that.

Caching

If bottom-level directories have .rubocop.yml and caching is enabled then changing of hooks in top-level config will be ignored. Need to figure out how to handle it properly.

Testing

config context won't work here because aliases configuration is loaded on gem loading and doesn't fully use rubocop config loading mechanism. I think instead it's enough to test just aliases configuration loading though.