fix: [FIND-033] Force-cancel capability for all corporate action types.

[jaime-iobermudez]

This pull request introduces a new force-cancel capability for all corporate action types, allowing privileged admins to forcibly cancel actions such as coupons, dividends, votings, balance adjustments, and amortizations, regardless of their execution or record date. This is accomplished by adding a new admin role and corresponding methods and events for each action type, ensuring stuck or already-executed actions can be unblocked in a controlled way. Each force-cancel method retains the same access and state guards as the regular cancel methods, except for the date guard, and emits a dedicated event upon successful cancellation.

Force-cancel capability for corporate actions

• Added a new CORPORATE_ACTION_CANCEL_ADMIN_ROLE constant to roles.sol, granting privileged admin rights for force-cancelling corporate actions.
• Implemented force-cancel methods for each corporate action type:
  • forceCancelCoupon, forceCancelDividend, forceCancelVoting, forceCancelBalanceAdjustment, and forceCancelAmortization in their respective storage wrappers and facet contracts. These methods bypass execution/record date checks but retain other access and state guards. [1] [2] [3] [4] [5] [6] [7] [8]
• Updated function selectors and interfaces to expose the new force-cancel methods in each facet and interface. [1] [2] [3] [4] [5] [6]

Event and documentation enhancements

• Added new events for each corporate action type to signal when a force-cancel occurs: CouponForceCancelled, DividendForceCancelled, VotingForceCancelled, ScheduledBalanceAdjustmentForceCancelled, and AmortizationForceCancelled. [1] [2] [3] [4]
• Updated documentation and comments to clearly describe the purpose, restrictions, and behavior of the new force-cancel methods and events. [1] [2] [3] [4]

Role and import updates

• Updated imports in relevant files to include the new admin role and event dependencies. [1] [2] [3]

These changes provide a robust administrative mechanism to resolve stuck or problematic corporate actions while maintaining strict access control and auditability.

Type of change

• Bug fix 🐞
• New feature ✨
• Breaking change 💥
• Documentation update 📖
• Refactor 🔧

Testing

Node version:

• 20
• 22
• 24

Checklist

• Style Guidelines followed ✅
• Documentation Updated 📚
• Linters - No New Warnings ⚠️
• Local Tests Pass ✅
• Effective Tests Added ✔️
• No reduction of Coverage ✅

[marcosio]

Is possible to reuse the new code in the older?