Update Acknowledgements for 4.37

[github-actions]

Update the list of contributors in the Acknowledgements for 4.37.

Adjustments to the lists of contributors:

• Replaced profiles:
  None
• Profiles with inconsistent git author names:
  To avoid this in the future, please ensure you use the same author names across all your local git repositories (e.g. by setting git config --global user.name "Your Name") and across devices!
  If the selected name, simply the longest one (and marked in bold), is incorrect, please let us know.
  None
• Excluded bot-accounts:
  • @eclipse-releng-bot
  • @dependabot[bot]
  • @eclipse-platform-bot
  • @eclipse-jdt-bot
  • @eclipse-pde-bot
  • @eclipse-equinox-bot

Please verify these adjustments for correctness and grant those who are affected sufficient time to refine the adjustments.

[HannesWell]

This was triggered by the last test run of

• [RelEng] Automate more tasks in promotion/publication jobs eclipse.platform.releng.aggregator#3229

I actually expected it to not create a PR as there a no new contributors, but I forgot the Last revised field...
Technically it's correct to update it as the list was revised, but I think this causes unnecessary noise.
I can update the job to avoid updating only that date.
Or do you others think we should keep updating it?
Or is that field irrelevant any ways and we should remove it? I just added it back then because it was there before.

[akurtakov]

IMO the commit date serves the same purpose and can probably be used for display purposes.

[HannesWell]

IMO the commit date serves the same purpose and can probably be used for display purposes.

Do you suggest to read it from the GH API dynamically and substitute it when rendering the markdown on the client-side?

[HannesWell]

IMO the commit date serves the same purpose and can probably be used for display purposes.

Do you suggest to read it from the GH API dynamically and substitute it when rendering the markdown on the client-side?

Will look into this later.
For now I'm closing this, to allow a new run of the job to (re-) generate the acknowledgements can start in a fresh PR.