[CI] Fix workflow dependency when publishing a new release branch

[straight-shoota]

#561 automated the process of publishing release branches.

There is a problem with dependencies: Deploy config finishes before Deploy book and in the time between, redirects to the new releaset (for example /reference -> /reference/1.4) are already in place but the target is not yet available.

So we need to delay the Deploy config workflow to run only after Deploy book has finished successfully. I suppose we could use the workflow_run trigger for this, but then we can't depend on the create branch trigger.
This means the deploy config would run on every build of a release branch. Maybe that's okay okay. Maybe we can still find a way to run it only when a new release branch is created (for example, check with S3 if the release folder already exists before pushing it). But that's definitely more complex. Probably best is to start with a config renewal on every build.