Replacement allocations use unpromoted job versions

[schmichael]

Nomad version

v0.12.0

Issue

When using deployments with canaries, replacement allocations created when an old allocation was stopped with nomad alloc stop 1234 incorrectly use the new unpromoted canary Job version instead of the last promoted/stable Job version.

Reproduction steps

1. nomad run example.nomad
2. Bump "V" env var or make some other change to example.nomad that will cause a destructive update
3. nomad run example.nomad
4. Observe the deployment has 1 canary alloc at job v1
5. nomad alloc stop <alloc id @ job v0>
6. Observe the replacement alloc is v1, not v0

Expected behavior

Replacement allocations should be the last promoted/stable Job version until the new canary is promoted.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.