Static `Client ID` id for OIDC configuration

Current Zitadel APIs support static (passed-in) IDs for some entities, but does not do so for others. For example Users can have custom userIduserId provided trough API, but an Application Client only has a dynamic one (generated by Zitadel instance). This poses some issues in cases where we have an event-driven system, that utilizes Zitadel APIs. We can't create static events (seeds) for dynamic ids. Those are only produced as "side effects". Have you considered to use static (passed-in) ids for all entities in Zitadel or maybe this issue came up in any Zitadel team discussions?