[prathshenoy]

Summary

What:

• Save each request’s build association before handing the build to status polling and analysis.
• Reuse the associated build when dispatch is retried.

Why:

• Let work registered before build dispatch find the build while it is running. Previously, the request only identified its build after completion, so ordered issue tracking could not follow a running validation.
• Avoid starting another build when retrying a handoff after the association was saved. A crash before saving it can still create a duplicate, so this does not guarantee exactly one CI build.

Test Plan

• Add unit tests.

Revert Plan

• Revert the dependent tracking change first, then revert this PR. Keep the additive database column; older code can ignore it. Provision the column before deploying this change.

Issue Links

• CODEM-607

Stack

1. fix(stovepipe): Retain request build associations #1011
2. fix(stovepipe): Track validations in order #1010