Tenant Migration related jstests should call donorForgetMigration when migration is completed(aborted/committed). Failure to do so will make the recipient to exhaust the TenantMigrationRecipientService thread pool (default is 8, see SERVER-50669). Currently, there are components on the recipient side, like oplog fetcher and cloner, which runs a synchronous task on the TenantMigrationRecipientService thread pool without yielding the thread. Those components will be stopped only if the migration on recipient side fails due to an error or receives RecipientForgetMigration cmd.