Use strategies from SCM to the build name job

[Turiok]

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

close #166

Instead of using the full display name of the job. It's using the value of ChangeRequestStrategy of the MergeRequestSCMRevision object

[spidey]

Nice! Looks good. A simple change will have the bug fixed.

[spidey]

Repeating my comment on the issue:

Managed to reproduce the issue with publish plugin from Jenkins plugin marketplace and then the branch proposed without the issue. Tested all 3 configurations successfully: MR revision, merged result and both together.

It's ready to be merged in my opinion.