After moving account to from Level 1 OU to level 2 OU under a different Level 1 OU CfCt deletes stacksets deployed to account

After moving accounts to from Level 1 OU to level 2 OU under a different Level 1 OU CfCt deletes (or attempt to delete) stacksets deployed to account

To reproduce create and enroll an account using Account factory in a level 1 OU as shown. Use CfCT to deploy a stack within the account, using its parent OU as a deployment target.
Move the account to a level 2 OU as shown in diagram.
Ensure all OUs and accounts are registered with CT
Execute CfCT pipeline.
Review logs - search for Router FunctionName: delete_stack_instances, Deleting Stack Instance: CustomControlTower-<stacket name>

Root OU
|
+- Source Level 1 OU (CfCT stackset deployment target)
|  |
|  +- Account position before move
|
+- Dest Level 1 OU (CfCT stackset deployment target)
   |
   +- Dest Level 2 OU
      |
      + Account position after move

Expected behavior is the stack deployed within the account is not deleted because at all times it remains under a deployment target.

Please complete the following information about the solution:

[X] Version: [e.g. v1.0.0] v2.3.0

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0089) - customizations-for-aws-control-tower Solution. Version: v1.0.0". You can also find the version from releases

[X] Region: [e.g. us-east-1] ap-southeast-2
[X] Was the solution modified from the version published on this repository? No
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[X] Have you checked your service quotas for the sevices this solution uses? Yes
[X] Were there any errors in the CloudWatch Logs? Search for the name of the stackset in the logs. Yes

aws-solutions / aws-control-tower-customizations

After moving account to from Level 1 OU to level 2 OU under a different Level 1 OU CfCt deletes stacksets deployed to account #118