components can use relative imports to reach their own files. cross components imports can't work reliably (import conflicts, version changes etc)

Pull Request Test Coverage Report for Build 849

• 0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 4.567%

Totals
Change from base Build 848:	0.0%
Covered Lines:	19
Relevant Lines:	416

💛 - Coveralls

@redbaron The reason this PR is WIP is because I'm not sure this is a good idea. With the introduction of modules, there is a conflict with projects that have decided to use directories under components.

What is module?

Another argument against this change would be case where same package (prototype) is installed as different component names, we use it internally where generic-app is pulled in multiple times under different names by same app. Although currently all of them are using same pkg version, in the future there might be a case where some components are going to use different versions of the same pkg

@redbaron a module is a directory underneath components. Previously, it was a flat namespace. In order to support more flexible configurations, modules were introduced.