Migration - New setting to turn enable or disabled migration package owner to execute it even if approved.

Is your feature request related to a problem? Please describe.

For SOX, we can't have the Creator of a Migration Package Deploy their own Package (Even if approved). Currently, once a Package is approved, the creator can deploy the Package.

Describe the solution you'd like

Person A - A TM1 Developer and developed a solution to be promoted to PRD. Person B - A TM1 Developer (Not Person A) Person C - System Owner/Team Lead/Product Owner (Part of Notification group: Control Owner)

Person A: Can create Package with ID #00001 Can request approval to Notification Group: Control owner. Can't approve based on Security Group CAN't deploy Package ID #00001 (Whether the Package #00001 is approved or not approved. Author can't deploy their own Package)

Person B: Can't approve based on Security Group Can't deploy package if not Approved. Once Package ID #00001 is Approved, they can Execute/Deploy Package ID #00001 BECAUSE THEY AREN't the Auther of the Package.

Person C: Can't create a Package with group Security Can Approve a Package as they have 'Approve Package' security.

Describe alternatives you've considered

Nonavailable, except manual controls.

Additional context

Add a config where a creator/author can't deploy a package where they are the creator/author.