Cruisecontrolrb Cruise Control.rb

CCRB-40 asked for triggering a slow build after a fast build succeeds, where the slow build should build the same revision that succeeded in the fast build. Presumably some version of the code supported that, BUT CCRB-155 complained about the assumption that the triggered build was building code from the same svn repo as the triggering build. (This assumption is totally valid for the fast-build-slow-build case, but presumably someone was looking to use the trigger for a different scenario.) While the change made to SuccessfulBuildTrigger to address this CCRB-155 may work for that other scenario, It broke the original fast-build-slow-build scenario CCRB-40 described. The intent of the change (based on Alexey's write-up in CCRB-155) was to abandon the idea of getting the revision from the triggering build and just have the triggered build build the latest revision, but it uses the triggered project's last_locally_known_revision (Last Changed Rev from svn info). This means it rebuilds whatever revision it has in its working copy (i.e, it keeps rebuilding the same revision every time).