[doc] Decrease number of retries for puppet deployments

Few questions:
1) where do we document how many retries we do?
2) It might be fine to run 2 times instead of 3, tnough it has nothing to do with fail fast during testing. Our tests must fail after even first pass, so we should not wait 2 runs actually at all. Let's figure our how we can make it happen. May be additional deployment param passed via REST API, which would go thru to Astute?

> 1) where do we document how many retries we do?
As i know, we do not notice about such detail in documentation.

> 2) Our tests must fail after even first pass, so we should not wait 2 runs actually at all
If we setup zero retries in test, we should also specify such behavior for production. In other case we will get tests that run with different condition and show different result. 1 retry in other case as Dmitry Illyin explain me, sometimes can solve some problem with puppet graph.

Sure, decrease number of retries to zero looks like desirable goal. We can create patchset with zero retries and run all tests in parallel with master iso. If result will be the same, apply it to master. What do you think?

After discussion with Mike Scherbakov (mihgen) original idea is to use debug mode for fast CI test which can save for us a lot of time.

System tests and BVT still should use puppet runs with retries.

Related with: https://bugs.launchpad.net/fuel/+bug/1343136

Is this just a change to the number of times puppet scripts are run before failing to the customer? If so, is it necessary to expose this to the customer? I see this as targeted to 6.1 - is anyone really reading the 6.1 release notes to see this kind of information now?