Better deprecation warning for editor integration

Hi!

Here

https://github.com/Gillespie59/eslint-plugin-angular/blob/cd58df172c1561994ce980bc9d9042f7a4b11c15/rules/service-name.js#L72

you just `console.warn` which lands on stderr. For SublimeLinter we parse stderr for common errors. It would be way easier to parse this message if you reword this. E.g. `DeprecationWarning: ....`.

Start in rules/service-name.js at line 72, where the deprecation message is sent to stderr, and read the surrounding rule logic. Check how SublimeLinter parses stderr, then verify that the warning has an explicit deprecation prefix and remains understandable to users.

Written by the indexing model from the issue text.