Summary:
Modified the rollback upgrade process to perform catalog upgrades during YSQL major upgrades only when all masters were successfully upgraded in the preceding software upgrade task.
Key improvements:

 - Replaced unreliable per-node version checks with persistent state tracking to determine catalog upgrade rollback eligibility
 - Introduced state storage during software upgrade to capture whether catalog upgrade rollback is permissible
 - Added retry protection to prevent redundant catalog rollbacks when masters have already been rolled back during upgrade retries

This change ensures more reliable catalog upgrade decisions during rollback operations and eliminates race conditions that could occur with the previous version-checking approach.
Original diff/commit: 5cac4a2a1c/D45677

Test Plan: unit and itest

Reviewers: anijhawan

Reviewed By: anijhawan

Subscribers: yugaware

Differential Revision: https://phorge.dev.yugabyte.com/D45681