Run short e2e tests only for code changes

[furkatgofurov7]

What this PR does / why we need it:
We run e2e tests in every PR and current workflow defines the type of actions to run e2e short tests are as following:

on:
  pull_request:
    types: [opened, edited, synchronize, reopened, labeled, unlabeled]

Description of each activity type:

• opened: Triggered when a new pull request is opened.
• edited: Triggered when an existing pull request is edited.
• synchronize: Triggered when a pull request's head branch is updated (e.g., new commits are pushed to the branch).
• reopened: Triggered when a closed pull request is reopened.
• labeled: Triggered when a label is added to a pull request.
• unlabeled: Triggered when a label is removed from a pull request.

Personally, it seems too much to re-run whole e2e-short tests when just editing PR description or labeling/unlabeling (it does not matter for us, because we don't have a selective test mechanism based on PR labels) of PR happens (in fact it happens to me a lot and that always re-runs the job which takes as of now ~1h). So, I would like to re-run e2e-short tests only when it is required: in new/re-opened PRs, code change pushes.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

• squashed commits into logical changes
• includes documentation
• adds unit tests
• adds or updates e2e tests

[Danil-Grigorev]

Personally, it seems too much to re-run whole e2e-short tests when just editing PR description or labeling/unlabeling

Agree, LGTM, thanks!