Remove deprecated automatic attribute binding

Author: Turbo87

README.md

@@ -20,9 +20,6 @@ Features
 - Removes properties starting with `data-test-` from your JS objects like
   component classes for production builds
 
-- Automatically binds properties starting with `data-test-` on all components
-  for development/testing builds
-
 More information on why that is useful are available on our
 [blog](http://simplabs.com/blog/2016/03/04/ember-test-selectors.html)!
 
@@ -79,20 +76,6 @@ be applied to the element that has `...attributes` on it, or on the component
 wrapper `div` element if you don't use `tagName = ''`.
 
 
-### Usage with Curly Components
-
-If you still use the old curly invocation syntax for components you can pass
-`data-test-*` arguments to the components and they will automatically be bound
-on the wrapper element too:
-
-```handlebars
-{{spinner color="blue" data-test-spinner=true}}
-```
-
-Please note that the automatic argument binding only works for components based
-on `@ember/component`, but not `@glimmer/component`.
-
-
 ### Usage in Ember addons
 
 If you want to use ember-test-selectors in an addon make sure that it appears

addon/utils/bind-data-test-attributes.js

@@ -26,7 +26,10 @@ module.exports = {
       this._stripTestSelectors = !app.tests;
     }
 
-    this._shouldPatchClassicComponent = !this._stripTestSelectors && addonOptions.patchClassicComponent !== false;
+    if ('patchClassicComponent' in addonOptions) {
+      ui.writeDeprecateLine('[ember-test-selectors] The `patchClassicComponent` option is obsolete. ' +
+        'You can remove it from your `ember-cli-build.js` file.', false);
+    }
   },
 
   _setupPreprocessorRegistry(registry) {
@@ -70,10 +73,6 @@ module.exports = {
 
       this._registeredWithBabel = true;
     }
-
-    if (this._shouldPatchClassicComponent) {
-      host.import('vendor/ember-test-selectors/patch-component.js');
-    }
   },
 
   cacheKeyForTree(treeType) {
@@ -85,13 +84,6 @@ module.exports = {
     }
   },
 
-  treeForAddon() {
-    // remove our "addon" folder from the build if we're stripping test selectors
-    if (this._shouldPatchClassicComponent) {
-      return this._super.treeForAddon.apply(this, arguments);
-    }
-  },
-
   preprocessTree(type, tree) {
     // remove the unit tests if we're testing ourself and are in strip mode.
     // we do this because these tests depend on the "addon" and "app" folders being available,