yaql limits not correctly set on stable/newton

The problem this fixes is with large stacks we hit the default (small) limit iterators of 200, resulting in errors when fairly large (few tens of compute nodes) overcloud deployments are attempted.

There were two patches fixing this, we're missing the one from larsks:

https://review.openstack.org/#/c/377782/

https://review.openstack.org/#/c/382056/

To clarify the first patch landed before we branched stable/newton, but it was broken so this second patch fixes the syntax and actually increases the limit_iterators value from the too-small-for-tripleo value of 200 to 1000.

Stable backport proposed:

https://review.openstack.org/#/c/398396/

Reviewed: https://review.openstack.org/398396
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=bedf20ec794bb878f64c4ccf5a3d4ecee1d892de
Submitter: Jenkins
Branch: stable/newton

commit bedf20ec794bb878f64c4ccf5a3d4ecee1d892de
Author: Lars Kellogg-Stedman <email address hidden>
Date: Tue Oct 4 15:56:07 2016 -0400

    correctly spell yaql_limit_iterators

    A recent change (55ccd0e) introduced support for the yaql_memory_quota
    and yaql_limit_iterators options in puppet-heat, but omitted the yaql_
    prefix on limit_iterators.

    Closes-Bug: #1642287
    Change-Id: Ice258c8afcb501b1742487c3de572121dbec8a44
    (cherry picked from commit 2c7c869699e8d1fe8eba10ddfcee531abad2dc7f)

This issue was fixed in the openstack/instack-undercloud 5.2.0 release.