standalone quickstart should be updated to use the container prepare commands instead of a template

[Alex Schultz]

We should update the standalone deployment in quickstart to use openstack tripleo container image prepare rather than generating the ContainerImagePrepare variable in the jinja templates.

https://github.com/openstack/tripleo-quickstart-extras/blob/9ae6212f001051f349c72484b9e9cb347aa13eca/roles/standalone/templates/standalone_config.yaml.j2#L4-L14

The docs recommend using the command to generate a containers-prepare-parameters.yaml.

https://docs.openstack.org/tripleo-docs/latest/install/containers_deployment/standalone.html

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/604487

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/604487
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=c193a2ff2adea4bd5f744f7c7920b394670e268f
Submitter: Zuul
Branch: master

commit c193a2ff2adea4bd5f744f7c7920b394670e268f
Author: Alex Schultz <email address hidden>
Date: Fri Sep 21 15:52:10 2018 -0600

    Update standalone container prep steps

    The existing configuration no longers represents the documented way to
    install the standalone. This change pulls the container prep data out of
    the standalone_parameters.yaml and puts it in it's own environment file
    which is generated using the openstack triple container images prepare
    command.

    Change-Id: Ic57048f517255d04b31b2a33ac5f70337aca6e68
    Closes-Bug: #1793233

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-quickstart-extras 2.1.1 release.