fix($parse): allow arguments to contain filter chains

[petebacondarwin]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

fix

What is the current behavior? (You can also link to an open issue here)

call expressions cannot take filter chains as parameters

What is the new behavior (if this is a feature change)?

call expressions can take filter chains as parameters

Does this PR introduce a breaking change?

No

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
• Tests for the changes have been added (for bug fixes / features)
  - [ ] Docs have been added / updated (for bug fixes / features)

Other information:

Closes #4175
Closes #4168

[gkalpak]

LGTM (as long as Travis is happy)

[Narretz]

Does this impact performance?

[petebacondarwin]

@Narretz - no real impact on performance. The filterChain method looks like this:

``js
filterChain: function() {
var left = this.expression();
var token;
while ((token = this.expect('|'))) {
left = this.filter(left);
}
return left;
},

You can see that it is calling straight through to `this.expression()` anyway, and then if the next token is not a pipe it falls out.