[WC-1550]: Handle pnpm install failure in dependabot PRs

[iobuhov]

Description

This PR introduces new build step, to handle pnpm install step failure on dependabot PRs
This step is meant to update pnpm-lock.yaml file on Dependabot
pull requests. Right now dependabot not work fine with monorepos
so we have to do extra work to automatically update lock file.
This step is part of "check" job, but could be part of any other job.
We put it here just because previous Install dependencies step is just
first "install" in this workflow.
The idea of this step - if install fails, try to fix lock file, commit and
push changes.
NOTE: we use magic string ([dependabot skip]) to allow branch rebase, read more at link below.
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#allowing-dependabot-to-rebase-and-force-push-over-extra-commits

Pull request type

• No code changes (changes to documentation, CI, metadata, etc)
• Dependency changes (any modification to dependencies in package.json)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Test related change (New E2E test, test automation, etc.)

What should be covered while testing?

• After merging this PR we need to instruct dependabot to rebase one or two PRs and see if failure handling executes correctly.

[iobuhov]

cc: @leonardomendix