refactor: use attributes for directives matching

[pkozlowski-opensource]

This refactoring changes the compiler logic so directives and their bindings are matched against attributes instead of matching property bindings. This is based on the following reasoning:

• attribute and property names are not always equal (ex. in a template we want to write <input read-only="exp"> while the corresponding property binding should be readOnly)
• people want to express directive selectors as targeting normalized attribute name (ex.: for an element like <input [read-only]="exp">, <input bind-read-only="exp"> I want to always express my attribute selector as [read-only])

[pkozlowski-opensource]

This is pre-requisite for fixing #866

@mhevery I hope that his is the change you had on your mind during yesterday's discussion.

[pkozlowski-opensource]

@tbosch this is the PR I've mentioned during the stand-up. Please ping me if you need any additional info.

[tbosch]

Remove propertyBindings from createPipeline in this spec (clean up) and move this test up into integratation_spec.js

[tbosch]

Also remove variableBindings, this should follow the same rules as propertyBindings

[tbosch]

Same there, move one of the tests for variableBindings up into integration_spec

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}