Git-machete

- Add an action to automatically squash the commits belonging to the given branch.

- Add support for IntelliJ 2022.2.
- Show a path to repository (from project root) instead of a repository name alone in the repository selection combobox.

- The <i>Pull</i> action displays custom notification message when it is executed on branch that no longer exists remotely

- Fix docs on the shortcut that opens Git Machete Tab <i>(command option shift M)</i> on Mac.
- <i>Merge Parent Into Current</i> action has been added.
The action merges a parent branch into the current branch, as suggested by mkondratek and pedroadame.
- Dropped support for IntelliJ 2020.1 and 2020.2.
- The <i>Pull</i> action on specific branch displays additional information whether fetch has been performed before fast-forward merge, as suggested by micpiotrowski.

- Squash-merges are now detected (and marked with gray edge) as in git-machete CLI &mdash; first suggested by asford.
- The reoccurring problem with <tt>AlreadyDisposedException</tt> (reported by yeahbutstill) is now hopefully solved.
- The <i>Pull</i> action fetches all branches from the remote.
Pulling a branch now behaves consistently with <tt>git pull</tt> by fetching all branches.
- <i>Show in Git log</i> action has been added to per-branch context menu options.
The action points to a branch (its latest local commit) within IntelliJ's built-in Git log, as suggested by KotlinIsland.

- The slide-out dialog displays name of the branch to be slid-out and potentially deleted (contributed by DcortezMeleth).
- Change machete file location for worktrees to the top-level .git/machete (rather than .git/worktrees/.../machete), as reported by jeffjensen.
This location is now compatible with git-machete CLI.
- Provide separate code style settings for machete files.
Opening machete file in editor no longer changes global code style settings for Other File Types, as reported by radeusgd.