puppet-lint retry failures blocking stx-config submissions

[Al Bailey]

The zuul-cloner used by the puppet-lint tox job in stx-config is failing on certain nodesets in zuul.
This is because zuul-cloner is deprecated by Zuul3, and not all zuul nodes have it.

The fix is to remove the zuul-cloner code completely from the pre.yaml

This will unblock reviews that are failing with
  /bin/bash: line 21: /usr/zuul-env/bin/zuul-cloner: No such file or directory

and retry_failure reported in the zuul jobs.

(not following the template for this bug, I already have a fix ready, and that will unblock my other commits)

[Al Bailey (albailey1974)]

Review is https://review.opendev.org/#/c/667619/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/667619
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=389d7b785f8f595aab67d15abc1f9b1af4de7847
Submitter: Zuul
Branch: master

commit 389d7b785f8f595aab67d15abc1f9b1af4de7847
Author: Al Bailey <email address hidden>
Date: Wed Jun 26 08:57:17 2019 -0500

    Fixing puppet-lint failures in zuul

    puppetlint zuul jobs are timing out.
    The problem is that zuul-cloner is being used, which is deprecated.
    This fix removes the zuul-cloner code from the pre job.

    Change-Id: Ib34b5b226c7cc5ace8917e513a901596b39b8f8e
    Closes-Bug: 1834350
    Signed-off-by: Al Bailey <email address hidden>

[Ghada Khalil (gkhalil)]

Marking as stx.2.0 release gating; critical priority given this is preventing code merges