plugins best practices

I've updated the plugins best practices reflecting advancements that was made over the years since the epic [Plugin namespacing: A good solution?](https://groups.google.com/d/msg/simple-build-tool/cCCYbopR6JQ/CslOL4TCb7IJ) thread that started this page.

It's more opinionated (avoid commands, provide feature in `object`) and strongly worded about things that previously waffled (I removed the bit about task scoping being optional because that disclaimer predates `::` notation in the shell). /review @jsuereth 
I'm at the point I agree :).    Maybe we should make a note about how configurations should, ideally, be tied to ivy-style configurations.  If you need a new classpath or set of artifacts, you probably need a  new configuration (like integraiton test vs. test).