Extend BC example for feat($compile) in > Angular 1.6.0 docs

[lbayerl]

Do you want to request a feature or report a bug?
issue in doc - wanted to create PR but couldn't.

What is the current behavior?

in CHANGELOG.md there is this BC description for feat($compile): https://github.com/angular/angular.js/blob/master/CHANGELOG.md#breaking-changes-1 regarding the 'binding' in 'components'

What is the expected behavior?

The same behaviour exists when you use the controllerAs pattern like e.g.

  angular
    .module('myApp')
    .directive('myDirective', myDirective);

  function myDirective() {
    return {
      restrict: 'E',
      scope: {
        value: '='
      },
      controller: 'myController',
      controllerAs: 'vm',
      bindToController: true,
      templateUrl: 'myTemplate.html'
    };
  }

You want have access to vm.value in your Controller.

What is the motivation / use case for changing the behavior?
Extend the example for the BC.

**Which versions of AngularJSare affected by this issue?
All version > 1.6.0

[gkalpak]

I don't think we need to extend the example (as it would get really verbose), but the current description can indeed be confusing, because it only mentions "component constructors".

👍 for changing the description to something like: component constructors --> component/directive controller constructors

(BTW, the change needs to be applied both to the changelog and the migration guide.)

[lbayerl]

Find with that as well - it took as a while to find out what's going on here - therefore I thought providing an additional example could help. But again as said, your approach seems good enough to me.