Feature: improved initialisation commands

[marblegravy]

Following on from the troubleshooting in #12 I've modified the ahoy files to include a few extra options to stop anyone else running in to similar issues.

My scenario is uncommon because I have multiple versions of govCMS scaffolds for different purposes, but what I didn't understand was that my other projects were 'leaking' their modified containers in to this one.

It's possible that others could find themselves in a similar boat in future.

To mitigate this, I've proposed that the readme uses a different command ahoy init when you first set up the project that will force it to use the exact containers specified and not cached versions that might already exist on the users machine.

I've also created an additional command ahoy rebuild that does the same thing but with the idea that if someone has been working on a project for a long time and updates have been made upstream, that they may want to effective force refresh and get the latest version of everything back to a known good state.

Finally, I've added in a link to the Lagoon troubleshooting section (from the old lagoon docs as this section hasn't been moved to the new version yet that I could see) at the bottom of the readme.

Hopefully these small mods should mean all future users can reliably generate the scaffold exactly as intended regardless of what else they may have installed previously.

[simesy]

My view expressed elsewhere is that the ahoy file needs a massive shakedown.

[marblegravy]

@simesy - shakedown how? To simplify it, just re-write it, add more functions or a combo of the two?