Add push-new-tag and retires

[NiedziolkaMichal]

This PR consists of 3 parts:

1. I am adding push-new-tag and retries inputs, which will allow to create and push the generated tags to the remote repository. This will allow us to remove a concurrency group in ci.yml of opbox-web.
   The retries is important, because two developers might trigger CI at exactly the same time. This case was tested in here: https://github.com/allegro-internal/opbox-web/actions/runs/7473729159/job/20338446162

To https://github.com/allegro-internal/opbox-web
 ! [rejected]            v11.9538.1-RC.8 -> v11.9538.1-RC.8 (already exists)
error: failed to push some refs to 'https://github.com/allegro-internal/opbox-web'
hint: Updates were rejected because the tag already exists in the remote.
From https://github.com/allegro-internal/opbox-web
 * [new tag]             v11.9538.1-RC.8 -> v11.9538.1-RC.8
To https://github.com/allegro-internal/opbox-web
 * [new tag]             v11.9538.1-RC.9 -> v11.9538.1-RC.9
Current tag: v11.9538.1-RC.8
Next tag: v11.9538.1-RC.9
Next version: 11.9538.1-RC.9

Those two new inputs are optional and disabled by default.

2. I am adding prettier, husky, lint-staged
3. Updating dependencies

Related PR: https://github.com/allegro-internal/opbox-web/pull/16397