[Bug]: Different behavior for listed vs. unlisted extensions when a new version is submitted after the previous blocked/restricted

[ioanarusiczki]

What happened?

While checking ux for #15198 I've noticed the following scenario:

1. a first version of an extension is auto-approved
2. version is blocked/restricted. The version is not force-disable at block.
3. a new version is submitted after the block

Listed blocked with new versions submitted (add-on was not force disabled at block/restriction but if it was then force-enabling is working from rev tools)
blocked https://reviewers.addons.allizom.org/en-US/reviewers/review/2244126
restricted https://reviewers.addons.allizom.org/en-US/reviewers/review/2244145
or a restriction is hardened https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/634906

Same scenarios with unlisted versions:
blocked https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-unlisted/634907
restricted https://reviewers.addons.allizom.org/en-US/reviewers/review-unlisted/2244107
soft block hardened https://reviewers.addons.allizom.org/en-US/reviewers/review-unlisted/2243988

What did you expect to happen?

Not sure how it's supposed to happen reason why I filed this.

Is there an existing issue for this?

• I have searched the existing issues

┆Issue is synchronized with this Jira Task