Proposing that we make the service names *just* a little bit longer
feature #4463 [BestPractices] Proposing that we make the service names *just* a little bit longer (weaverryan)

This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #4463).

Discussion
----------

[BestPractices] Proposing that we make the service names *just* a little bit longer

| Q   | A
| --- | ---
| Doc fix? | no
| New docs? | no
| Applies to | 2.3+
| Fixed tickets | -

Hi guys!

This is a very minor proposed change for the best practices, which I would like to consider. The original best practice was because we don't want people to blindly follow the 3rd party service naming that's quite long. In your own app, they just need to be unique within yourself. But personally, I *do* use things like `app.slugger`, because I like to be able to grep my codebase for a service and reliably find it.

Thanks!

Commits
-------

b1ceb88 Proposing that we make the service names *just* a little bit longer