fix: let the integ credentials outlive the CodeBuild build they poll

[andychoquette]

What

Add role-duration-seconds: 10800 to both configure-aws-credentials steps in reusable_integration_test.yml.

Why

aws-codebuild-run-build polls the build using these credentials, so the session has to outlive the build, not just start it. Neither step set role-duration-seconds, so both got the 1 hour default.

Integ builds already exceed that. deadline-cloud-for-3ds-max release 0.4.2 failed twice this way — attempt 1 died at 1h01m, attempt 2 at 1h00m:

##[error]The security token included in the request is expired

Meanwhile the build it was polling — deadline-cloud-for-3ds-max-mainline-windows-integ, started 2026-09-23 09:32 PDT — SUCCEEDED at 11:06, after 94 minutes. The tests passed. Only the poller's credentials ran out, and the release sat blocked on a green job it could never produce.

Margins

Source	Duration	Status
refs/tags/0.4.2	94 min	SUCCEEDED
mainline	48 min	SUCCEEDED
mainline (09-22, 09-18, 09-17)	48 min	SUCCEEDED

Even the routine 48-minute build left only ~12 minutes of headroom. Builds against refs/tags/* take roughly twice as long as the equivalent mainline build — 48 vs 94 minutes on the same day against the same code — so the release path is the one that goes over. That's worth investigating separately; it isn't addressed here.

Why 10800

Every *_IntegOIDCRole in the CI account already allows it, so no IAM change is required. Verified by matching RoleId from the failing job's Authenticated as assumedRoleId AROA5U2N4YCXWZP3KBWTX that the 3ds Max job assumes deadline_cloud_for_3ds_max_dev_IntegOIDCRole, MaxSessionDuration 10800; the other nine integ roles are all 10800 too.

Caller safety

Nine repos call this workflow: deadline-cloud, deadline-cloud-for-{3ds-max,blender,houdini,maya,unreal-engine,vred}, deadline-cloud-job-attachments, private-deadline-cloud-staging.

configure-aws-credentials fails fast when role-duration-seconds exceeds a role's MaxSessionDuration, so a caller whose role allowed less would break immediately and visibly rather than silently. The sub-10800 roles I found in the account (openjd-cli-*, Fortify*, bealine_client_software*) are not callers of this workflow.

Reviewer check: I could not map private-deadline-cloud-staging's integ role, so please confirm that one allows 10800.

Testing

Not exercisable outside a real integ run. Validated that the workflow still parses as YAML and that both credential steps carry the new value.