Now that we have "always on" server provisioning it's time to put it as the quickstart main user experience:

• ZIP distribution usage becomes an alternative, contained in a asciidoc section, where specifics like wildfly:deploy and wildfly:undeploy usage are detailed
• user experience always starts with a wildfly:dev command, which builds and starts the provisioned server, supporting live code changes  
• every additional runtime interaction instruction should be optimised considering server provision is the main local metal use case, and live code changes are on