rename stuff like options.js and /assets/ to names more sourcejs related

[ndelangen]

Now that install by dependency is going to become the official way and the only way in 0.7.x I think we should think about being a bit less invasive upon people's environment.

Imagine if every npm dependency just asked to add a options.js to the root of the folder?
I propose we rename it to something like sourcejs.config.js if that's possible.

Also I think all template-overrides, assets overrides and core-overrides could be in a sourcejs folder by default, instead of in the root.
Another options would be to rename them to sourcejs-assets, sourcejs-templates.. etc.

[robhrt7]

Hi,

My assumption always was that SourceJS should be defined as a dependency deeper in the tree, next to the project components. Do you see it's feasible to keep SourceJS as a dev dependency right in the root? In this case of course options.js is way too abstract. We can introduce an alternative name, with deprecation notice for the old one already in 0.6.0.

For the overrides, we definitely should namespace the core and assets folders, following the same deprecation flow as described above.