Deleting a child API in an aggregagtion does not update the subscription in Daikoku

[quentinovega]

Description

When deleting an API that participates in an ApiKey aggregation as a child extension, the extension (authorized entity) is correctly removed from the API key in Otoroshi, but Daikoku is not updated at all — the subscription remains as-is, still referencing the deleted API.

When the parent API is deleted, the extension is correctly cleaned up on both sides.

Steps to reproduce

1. Set up an Aggregation with a parent API and one or more child API extensions
2. Delete the child API
3. Check the subscription state in Daikoku and the API key state in Otoroshi

Expected behavior

Deleting a child API should remove its extension from the subscription in Daikoku and from the API key in Otoroshi.

Actual behavior

Deleted API role	Subscription updated in Daikoku?	Extension removed in Otoroshi?
Parent	✅ Yes	✅ Yes
Child	❌ No — subscription unchanged	✅ Yes

The deletion logic only handles the parent case. For a child, the Otoroshi side is correctly processed but the Daikoku subscription is left untouched, creating a desync where Daikoku still references an extension that no longer exists in Otoroshi.