Roles dynamically added with ngAria

To communicate the purpose of custom inputs with a type of `range`, `checkbox` or `radio`, ngAria now dynamically adds roles to custom radio buttons, checkboxes and sliders. Related issue: https://github.com/angular/angular.js/issues/10012

It also adds a role of `button` to any element with `ngClick` that is not a `button` or `anchor` element (such as a `div`). This feature comes on the heels of https://github.com/angular/angular.js/pull/10288, which binds the `keypress` event alongside `ngClick`. With these two changes together, users of assistive technologies will know what they are focused on and be able to operate controls with the keyboard (this is important because `ngAria` dynamically adds `tabIndex="0"` with `ngClick`). HOWEVER, not all uses of ngClick are used for buttons–sometimes developers bind `ng-click` on the document. In this scenario, a role can be overridden by the developer if `button` does not match expected behavior. Related issue: https://github.com/angular/angular.js/issues/9254

Note: This change does not implement any kind of flag allowing the user to opt out of roles being set. 
I wonder if it would be more readable to have something like `&& !IsNodeTypeOneOf(elem, "BUTTON", "A")` or something. I don't think it's problematic like this, but if there was one extra condition added it would be really hard to read.