When Public Base URL is updated zync updates the routes before proxyconfig is promoted

Current behaviour

If the Public Base URL in the APIcast integration is updated then an event is triggered and sent to zync to update the routes. This event is triggering the job before the proxyConfig object has been promoted.

Expected behaviour

If the Public Base URL in the APIcast integration is updated then an event is only triggered after the proxyConfig object has been promoted to ensure consistency of states between system, apicast & OCP routes.

The problem comes from the fact we expose proxyConfig settings on a Product page when in fact only 1 setting on that page is Product related, all the other settings are proxyConfig attributes. Should we change the form submission on this page to promote directly to the staging environment?