npm run release:publish should not result with an error

[mlewand]

📝 Provide detailed reproduction steps (if any)

During the 19.1.0 release after running npm run release:publish we had following error:

Pushing "ckeditor5" package...
To github.com:ckeditor/ckeditor5.git
 * [new tag]               v19.1.0 -> v19.1.0
 ! [rejected]              master -> master (non-fast-forward)
error: failed to push some refs to 'git@github.com:ckeditor/ckeditor5.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Error while executing git push origin master v19.1.0: To github.com:ckeditor/ckeditor5.git
 * [new tag]               v19.1.0 -> v19.1.0
 ! [rejected]              master -> master (non-fast-forward)
error: failed to push some refs to 'git@github.com:ckeditor/ckeditor5.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

This place should be adjusted: https://github.com/ckeditor/ckeditor5-dev/blob/e67b9e9c9dd484d575f301027929ac85129a37b6/packages/ckeditor5-dev-env/lib/release-tools/tasks/releasesubrepositories.js#L570

---

If you'd like to see this fixed sooner, add a 👍 reaction to this post.