Expose meta data to rules for the Ember version being used

This will allow rules to accommodate the best rules for a given Ember version. This would be helpful for a few existing rules (the recent rule RE: dynamic invocation without fn; the no-capital-arguments rule; and likely others).

There are a couple different logical paths to accomplish this:

• have the configuration provide the Ember version, something like:

  module.exports = {
    meta: {
      emberVersion: require('ember-source/package').version
    },
  
    extends: 'recommended',
  };
  

• attempt to resolve the version (resolvePackagePath relative to the configPath)

I think we could allow both options…

[Turbo87]

I think I’d prefer to use the existing rule configuration options system that we already have. It seems reasonable that the Ember version would be able to change the default value for config options, but I think we should ensure that all of these things are still overridable.

[bmish]

I’d be concerned about exposing the Ember version to rules for the following reasons:

• Greater rule complexity
• Greater testing burden, need to check behavior in each Ember version
• No existing precedent for exposing dependency versions to lint rules (ESLint)

As @Turbo87 suggested, I’d rather rely on rule options to tell the rules about specific features/preferences they should be aware of.

Now if we really need to have awareness of the Ember version somewhere, maybe the config itself (i.e. recommended) could detect the Ember version and configure the rules as desired. Although that makes the config a lot more complex…