Signed-off-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Bumps [@types/dedent](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/dedent) from 0.7.1 to 0.7.2.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/dedent)

---
updated-dependencies:
- dependency-name: "@types/dedent"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

…edent-0.7.2

build(deps): bump @types/dedent from 0.7.1 to 0.7.2

This compose for backport script failure method was a remnant from when
this action used a shell script to perform the git commands. Most
reasons were dead code.

The manual instructions still suggested to determine the commits to
cherry-pick by determining the common ancestor (merge-base) of the head
and base refs, first. However, this way has been abandoned for quite
some time now. This especially became a problem now that merge commits
can be skipped, meaning that the suggestion no longer produced a
reliable result.

Instead, we can simply suggest the same as the action does. It knows
exactly which commits to cherry-pick.

When the cherr-picking failed, it's very likely that there are
conflicts. We should instruct the user to cherry-pick locally and
resolve any conflicts.

The switch command has been around for 4 years now, and while still
marked as experimental, I think it's fine to "switch" to it in the
suggestion for local cherry-picking. It's unlikely that users are using
such old git versions that it doesn't support git switch --create.

…stion

Skip merge commits in suggestion

Signed-off-by: Nico Korthout <korthout@users.noreply.github.com>

Signed-off-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>