Unify angular service naming

[slaweet]

Expected behaviour

Research the best practices for angular service naming and update our code accordingly to make the naming consistent.

Actual behaviour

We have all sorts of naming (UpperCamelCase, camelCase, $camelCase):

Account        
dialog
passphrase
signVerify
delegateService
lsk
$peers

[slaweet]

While the services are updated, we can also look at the methods they offer and fix if parameters are unclear (e.g. param called options) or the method belongs to another service (getDelegate in forgingService).