Chore: move scaffolding configuration to a single folder

[leventebalogh]

What changed?
Created a .config/ folder in the scaffolded projects which is containing all the build and dev-tooling configuration that is needed to start working with the plugins. To make it more explicit I have left most of the configuration files in the root of the scaffolded project, but now they are extending the basic configuration living under ./.config. (Like this it is easier and safer to extend them I guess)

Why?
The main reason for experimenting with this was the need for being able to apply configuration updates to plugins more easily. It would be beneficial to provide a script which can update the configuration of previously scaffolded plugins - this could help us maintaining our plugin examples, and could also help plugin developers keeping their plugins up to date more easily.

Link to .config/README

[jackw]

Really like where this is going @leventebalogh ! 🚀 👏

[mckn]

I think this is great!! The only thing that I'm not super fond of is the naming of the folder. Would it make sense to call it .plugin, .build, .grafana or something a bit shorter`

[leventebalogh]

I think this is great!! The only thing that I'm not super fond of is the naming of the folder. Would it make sense to call it .plugin, .build, .grafana or something a bit shorter

@mckn Yea, sure! What would you say to .config? Or you find the term config/configuration a bit misleading?
I would probably not call it .build personally, because the term is often used to as a folder name for generated build outputs, but .plugin and .grafana can work 🤔

[mckn]

.config works for me!

[mckn]

LGTM! Go go go