fix(test): Don't execute change set instead of waiting for prompt

[lucashuy]

Which issue(s) does this change fix?

None

Why is this change necessary?

The integration test was stuck on Linux machines due to the process waiting for a prompt that never appears when running the deploy commands as a persistent command.

How does it address the issue?

Uses the existing --no-execute-changeset flag to create a change set and exit, instead of waiting for the prompt and killing the process.

What side effects does this change have?

None.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.