Change namespace from std::integration for build tool plugins

[tmpfs]

Update the example code in docs/in-depth/build-tools.

@chrism, I recently converted the build tool examples into blueprint plugins using the std::integration namespace so that people can do stuff like:

uwe new webpack-project std::integration::webpack
cd webpack-project
npm install
uwe dev

Because we have just removed the use of integrations in this context I think we should rename the plugin namespace.

Maybe std::build-tool, std::build or just std::tool instead? Or should we put them in the std::blueprint namespace?

They don't live in the blueprints repository and I am not treating them as officially supported so my preference is to avoid the std::blueprint namespace and use one of the other suggestions.

Got a preference for the new namespace?

[chrism]

Hey @tmpfs I like build because it is short, memorable and seems most relevant to what it covers.

If anything I see webpack more as the tool and the integration as more the pipeline of the build... if that makes sense?

[tmpfs]

Thanks @chrism std::build it is then! Will do that tomorrow and then the integrations renaming should be complete!

[tmpfs]

Closing as implemented, I went for a top-level build rather than the std::build namespace as these plugins are not part of the standard library.

Tested using this:

uwe new webpack-project build::webpack
cd webpack-project
npm install
uwe dev --exec