WBE request transition_timeout timeout not long enough

[Joshua Harlow]

When a worker is overloaded (or heavily loaded) or workers are still coming online the default timeout of 60 seconds may not be enough time for the sent task to transition out of the WAITING (submitted to worker but worker has not started it yet) or PENDING (no avaiable worker currently exits) state, when the timeout is always set to 60 seconds it can be painful to use the WBE in situations where it is more appropriate to set the timeout to higher or lower values (or infinite by setting the timeout to None).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/113623
Committed: https://git.openstack.org/cgit/openstack/taskflow/commit/?id=c491683650f0912b6bc613a5a819aaf4f32c4340
Submitter: Jenkins
Branch: master

commit c491683650f0912b6bc613a5a819aaf4f32c4340
Author: Joshua Harlow <email address hidden>
Date: Tue Aug 12 12:12:56 2014 -0700

    Allow WBE request transition timeout to be dynamic

    To enable longer (or shorter) timeouts for a WBE submitted
    request to transition out of the (PENDING, WAITING) states
    allow the transition timeout that was previously set to 60
    seconds to be provided as a WBE configuration option (it
    still defaults to the previously fixed 60 seconds when it
    is not provided).

    Fixes bug 1356002

    Change-Id: Idf384217004a334df03e2fff9150309fdfe08005