Feature Request: change cli folder to .au

Current behavior: aurelia cli creates and operates via project folder aurelia_project

Desired behavior:

create and operate via project folder .au fallback to aurelia_project if .au doesn’t exist

why less imposing folder name on the project tree. would be topmost folder name in the project tree. mimics other tooling’s convention (e.g. .vscode)

[grofit]

I kinda like this approach but I think currently the aurelia_project folder has too much responsibility, so currently it contains generator and aurelia config stuff as well as environmental vars and build tasks.

Almost every js project I have worked on before has a build folder and pushes tooling specific vars/config elsewhere, so it may be a compromise to have the .au folder for the aurelia.json and generators folder (as this is just project metadata and not required by a dev) and just put the environments and tasks folders into a build folder which is generally the norm for most js related projects. As when I first used CLI I was a bit confused where the generator had put my build script tasks.

[grofit]

The only thing I have noticed which makes me hesitant is that the aurelia.json is also used by the build (not gulp but the au CLI) for bundling etc so that kinda borders on doing 2 things, so I think this may need more thought as like mentioned earlier generally .somefolder implies its just metadata a dev never needs to play with (which should be true for the generators) but a developer may need to change the aurelia.json file.