Previous versions of a sequence continue to have `REVOKED` version status after the latest version was un-revoked

[tombch]

This table shows a sequence being created, then going through revision, revocation, restored, revoked again, restored again.

The previous versions are all still REVOKED, despite the latest version not being so, and the UI does not reflect them being revoked.

Something to consider is should they flip back to REVISED once the latest version is no longer a revocation.

[claude]

This issue appears to be related to #5446 (Collection of revocation related issues), which tracks various revocation-related problems. This specific bug about version status persistence could be added to that collection.

Also potentially related to #6425 which discusses improvements to how revocation versions are displayed, though that issue focuses on UI/UX improvements rather than the status logic bug described here.