New: Added no-trailing-spaces rule (fixes #995)

`on` perf:

```
CPU Speed is 2261 with multiplier 7500000
Performance Run #1:  2922.464079ms
Performance Run #2:  2915.99096ms
Performance Run #3:  2871.693ms
Performance Run #4:  2842.881841ms
Performance Run #5:  2869.45368ms
Performance budget ok:  2871.693ms (limit: 3317.1163202122952ms)
```

`off` perf:

```
CPU Speed is 2261 with multiplier 7500000
Performance Run #1:  2874.2219999999998ms
Performance Run #2:  2815.7648ms
Performance Run #3:  2869.23876ms
Performance Run #4:  2908.95748ms
Performance Run #5:  2862.79916ms
Performance budget ok:  2869.23876ms (limit: 3317.1163202122952ms)
```

I disagree that it's better or that it's a widely used pattern. Even if it were, that doesn't mean that it is good and clear code - I have also seen obtuse "factory/instance" patterns mimicking Java in wide use in some places, which I would not call good code.

> Also, this pattern is significantly faster on big matches count.

It is certainly not faster: http://jsperf.com/match-vs-replace-jr You can increase the length of the large test string as much as you want, match is always faster.

> $ will make pattern more difficult to understand and will not improve speed. That's subjective criteria.

`^` and `$` are some of the most basic regex symbols. If you expect your audience to know `[]` and `+`, then you can expect them to know about the anchors. And if you don't, you definitely should, because anchoring does indeed improve performance, and not just a little bit. It's not just about matching "line end", it's an anchor, and it means that instead of looking for a string of the form "whitespace, newline" anywhere in the input string (thus initiating a test on every character), the regex only needs to start looking for a match from the anchor. It's an order of magnitude difference and one of the simplest regex optimizations to make. You should use anchors whenever possible. And again, there is also the benefit that you don't need to worry about platform-specific line ends.