DB Error: constraint error during 5.56.2 upgrade. Authorize.Net (eCheck.Net) entity consider stale
When testing the most recent security upgrade, we got this error at the end of the process,
[Error: Finish core DB updates 5.56.2]
Exception: "API error: DB Error: constraint violation on payment_processor_type.delete( entity name Authorize.Net (eCheck.Net))"
#0 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/ManagedEntities.php(362): CRM_Core_ManagedEntities->onApiError()
#1 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/ManagedEntities.php(149): CRM_Core_ManagedEntities->removeStaleEntity()
#2 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/ManagedEntities.php(113): CRM_Core_ManagedEntities->reconcileEntities()
#3 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(417): CRM_Core_ManagedEntities->reconcile()
#4 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Upgrade/Form.php(799): CRM_Core_Invoke::rebuildMenuAndCaches()
#5 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Task.php(101): CRM_Upgrade_Form::doCoreFinish()
#6 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Runner.php(255): CRM_Queue_Task->run()
#7 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Page/AJAX.php(36): CRM_Queue_Runner->runNext()
#8 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Queue/ErrorPolicy.php(89): CRM_Queue_Page_AJAX::{closure}()
#9 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Queue/Page/AJAX.php(38): CRM_Queue_ErrorPolicy->call()
#10 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(285): CRM_Queue_Page_AJAX::runNext()
#11 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(69): CRM_Core_Invoke::runItem()
#12 /var/www/html/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php(36): CRM_Core_Invoke::_invoke()
#13 /var/www/html/wp-content/plugins/civicrm/civicrm.php(1199): CRM_Core_Invoke::invoke()
#14 /var/www/html/wp-includes/class-wp-hook.php(308): CiviCRM_For_WordPress->invoke()
#15 /var/www/html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#16 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action()
#17 /var/www/html/wp-admin/admin.php(259): do_action()
#18 {main}
We're using the Authorize.Net (eCheck.Net) processor type, which is the source of the constraint violation. Any thoughts as to why this would be caught up in a method to remove stale entities? I can post this as a core bug if need be.