Preserve Cause history.

Right now when you trigger a job retry with naginator it creates a new build with the same parameters, but does not preserve the cause history, which is important in many upstream/downstream job flows where you wish to maintain a view into the progress of a job as it progresses through a delivery pipeline. When relying on naginator to allow auto (or manual) retry of a given step in that pipeline due to sporadic environmental failures, it should maintain the cause history as to not break the delivery history of a given upstream/downstream flow.