Integrate work to date to perform end to end "dry run" settlement test

[evq]

Test 0: KMS key policy idempotency

Test 1: Worker hitting stub prepare / submit endpoints

Remaining work:

• [x] Do the test using the nitro-payments-dev branch ( should already have stub endpoints and workers )

Test cases:

• [x] Happy path: Create test payout report with 1 settlement, exercise CLI, we expect one prepare call, one submit call, workers run to completion
• [x] Worker prepare retry: Modify prepare endpoint to return error, deploy, create test payout report with 1 settlement, exercise CLI, we expect infinite prepare calls with backoff
• [x] Worker submit retry: Modify submit endpoint to return error, deploy, create test payout report with 1 settlement, exercise CLI, we expect one prepare call, infinite submit calls
• [ ] Attacker creates malicious KMS key: Create KMS key with malicious policy, run bootstrap command, should fail due to policy mismatch
• [ ] Bad PCR valid in bootstrap: Run bootstrap command with incorrect PCR value, should fail due to invalid attestation document

Test 2: Endpoints using dry run state machine ( exercises QLDB, signing, etc )

Remaining work:

• [x] State machine dry run functionality
• [x] Have endpoints call dry run state machine
• [x] Do the test

Test cases:

• [x] Happy path: Create test payout report with 1 settlement, exercise CLI, we expect one prepare call, one submit call, workers run to completion, introspect and verify history for created QLDB object
• [ ] Operator mistake: Create test payout report with 1 settlement, exercise CLI, we expect one prepare call, retry prepare - should return same document ids with an attestation, one submit call, workers run to completion, introspect and verify history for created QLDB object
• [ ] Wrong transaction authorization key: Create test payout report with 1 settlement, exercise CLI with test key from repo, we expect one prepare call, infinite submit calls - should fail, QLDB object should not enter authorized state
• [ ] Bad prepare attestation: Create build that includes invalid attestion response, create test payout report with 1 settlement, exercise CLI, we expect one prepare call, workers complete, prepare CLI tooling should report failure
• [ ] Wrong PCR value in prepare: Create test payout report with 1 settlement, exercise CLI with incorrect PCR value, we expect one prepare call, workers complete, prepare CLI tooling should report failure
• [ ] Attacker precreates object: Create test payout report with 1 settlement, precreate QLDB object under corresponding idempotency key but different details, exercise CLI, we expect one prepare call, one submit call - which should fail due to mismatched id, workers run to completion
• [ ] Attacker reverts object: Create test payout report with 1 settlement, exercise CLI, we expect one prepare call, one submit call, workers run to completion, introspect and verify history for created QLDB object, revert QLDB object to authorized state, rerun submit - should fail due to invalid history, workers run to completion

[Sneagan]

Test 2 Issues:

• 1817

• 1818

• 1819

• 1820

[husobee]

will work on creating bad kms key policy and bad pcr tests for cli tooling to wrap this up

[kdenhartog]

These should be done manually before finally closing out the security review for this project.

[kdenhartog]

marking this as blocking just as a last check to make sure we didn't miss anything. I'll handle this, so shouldn't require any additional work for this one to be closed out, but may produce new blocking issues.