Consistent file naming style

[bajtos]

In a slack-chat vote, we agreed to follow Angular's file naming convention in our project:

src/decorators/authenticate.decorator.ts

Now we need to clean up the code in loopback-next, loopback-next-hello-world, loopback-next-extension-starter (and possibly other repositories) to follow this new style.

Tasks

• Document the file naming style in our docs - either here on wiki, or preferably somewhere inside http://loopback.io/doc/en/contrib/code-contrib.html
• Decide on what convention to use for test file names - see the discussion here and here. Capture the convention in the docs.
• Update templates used by CLI to scaffold new projects, controllers, etc.
• Update loopback-next files to follow this convention
• Update other projects to follow this convention
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-hello-world
  • https://github.com/strongloop/loopback4-extension-starter (deprecated)
  • https://github.com/strongloop/loopback4-example-microservices
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-getting-started
  • https://github.com/strongloop/loopback4-extension-grpc
  • https://github.com/strongloop/loopback4-extension-typeorm (deprecated)
  • https://github.com/strongloop/loopback4-extension-mqtt
  • https://github.com/strongloop/loopback4-extension-graphql
    • rename graphql-component.ts to graphql.component.ts
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-log-extension
  • https://github.com/strongloop/loopback-next/tree/master/packages/example-rpc-server

Out of scope

• Automatic linter enforcing our file naming convention Automatic linter enforcing our file naming convention #833