Add support for .kitspace.yaml as well as kitspace.yaml

[Tyler-Ward]

Many tools and sites prefix their metadata files with a dot (originaly used to signify to linux to hide files), it might be worth adding support for this for the kitspace.yaml file so it can be easily identified as a metadata file by those viewing a project source.

[kasbah]

Might be a good idea. Sticking to one way has it's advantages too though: you get used to what it's called and where it is and can more easily find it. It's always meant to stay human readable and editable so I'm not sure making it a hidden file is the right call.

Some meta files that are not normally hidden include: package.json (JS), cargo.toml (rust), pyproject.toml (python). I admit these are normally the main "project" files and dictated by the language you use so I still might be convinced if enough people would really prefer to hide it.

open-source-rover folks would have preferred to put it in a sub-dir which is another consideration. 🤔