Feature proposal: Applying suggested changes should create "fixup" commit

Problem to solve

Applying suggested changes creates a new commit, but it would be cleaner and nicer if it was a fixup commit so that it can be squashed into the original commit and avoid clutter in the commit history.

Target audience

The merge request author (or other person fixing comments) will have an easier life applying fixes.

Proposal

When applying a suggested change on MR the commit that gets created should be a fixup commit so that it can be squashed correctly wiht git rebase -i -- autosquash.

What does success look like, and how can we measure that?

Same as proposal.

Links / references

https://docs.gitlab.com/ee/user/discussions/#suggest-changes