Differentiate between 'constructor' services and 'non-constructor' services in naming rules.

Why?
- There are different kinds of services, so it makes sense to have rules for distinctively naming them.
- Consider the following:
- Injecting `serviceName` as an argument provides a `constructor function`.
- Injecting `factoryName` as an argument provides a `value returned from a function`.

Suggested Implementation:
- Define a rule such as `angular/service-constructor-name` to target `constructor` services.
- Use `UpperCamelCase` as the default naming convention for `constructor` services.