Improvement of recommended action for "check-commit-message" run

### Description

If multiple commits are already available and one commit does not follow the glint rules, then an old commit might be required to be edited, such that git commit --amend does not work anymore.

Therefore please add:

* branch refs/pull/3055/head -> FETCH_HEAD
Commit bfaf83f422:
1: T1 Title exceeds max length (78>72): "DR-009-ACL-Concept: Added json scheme and reformatted json example to readable"
2: B4 Second line is not empty: "json"

Commit 8ca8fc5d44:
2: B4 Second line is not empty: "SOME/IP and IPC (and preparation for further use cases)"

WARNING: Your commit message does not follow the required format.
Formatting rules: https://eclipse-score.github.io/score/main/contribute/general/git.html
To fix your commit message, run:

git commit --amend
Then update your commit (fix gitlint warnings). Finally, force-push:
git push --force-with-lease

If the non compliant commit is not at HEAD use:
git rebase i (e.g. bfaf83f422)

Then for the affected commit rename *pick* to *reword*

Then save and enter.

Then the commit will be opened -> rework the commit

Then save and enter.

Then force push: git push --force-with-lease

### Analysis results

_No response_

### Solution

_No response_

### Error Occurrence Rate

None

### How to reproduce

_No response_

### Supporting Information

_No response_

### Classification

Minor

### First Affected Release

not released (main)

### Last Affected Release

not released (main)

### Expected Fixed Release

before release (main)

### Category

- [ ] Safety Relevant
- [ ] Security Relevant

Start by locating the implementation of the check-commit-message run's failure guidance and review how it identifies non-compliant commits. Update the recommendation to cover commits that are not at HEAD, using the rebase and reword procedure described in the issue. Verify that the output still explains amending the commit and force-pushing.

Written by the indexing model from the issue text.