Leverage gitmailmap for fixing authors' names

[peterfpeterson]

This PR gets rid of the custom work for fixing committer/author information to use functionality git already has.

gitmailmap is a built in git functionality for converting the random names/emails that people supply into something more meaningful. This includes correcting the names and email addresses.

There is no associated issue.

To test:

This added the ability to get the authors directly from tools/DOI/authors.py and can be run without accidentally creating a DOI. Use tools/DOI/authors.py --help to find out how to use it and try the two modes. As it says, you need to contact a TWG member (i.e. me) to get the .gitmailmap file.

This does not require release notes* because it modifies how authors are generated for the DOI tool.

---

Reviewer

Your comments will be used as part of the gatekeeper process. Comment clearly on what you have checked and tested during your review. Provide an audit trail for any changes requested.

As per the review guidelines:

• Is the code of an acceptable quality? (Code standards/GUI standards)
• Has a thorough functional test been performed? Do the changes handle unexpected input/situations?
• Are appropriately scoped unit and/or system tests provided?
• Do the release notes conform to the guidelines and describe the changes appropriately?
• Has the relevant (user and developer) documentation been added/updated?
• If the PR author isn’t in the mantid-developers or mantid-contributors teams, add a review comment rerun ci to authorize/rerun the CI

Gatekeeper

As per the gatekeeping guidelines:

• Has a thorough first line review been conducted, including functional testing?
• At a high-level, is the code quality sufficient?
• Are the base, milestone and labels correct?

[thomashampson]

I like that you can now run the authors.py script directly to print a list of authors for a given version. However, I think these points need to be addressed:

1. It does not return the names in "last_name, first_name(s)" format, as per the DOI schema.
2. It relies on a .mailmap file existing to map multiple aliases to each author. This would need to be hosted somewhere and updated by the technical release manager each release.
3. Some people may want there DOI author name to differ from their github name (e.g. Rob might want his formal name Robert to be his author name). This information is already captured in the existing translations list, and would need to be replicated in the mailmap.

[peterfpeterson]

All your points are quite valid. This moves the responsibility of correctly referring to committers to the mailmap file, which is maintained separately. Changes to the mailmap are as frequent as editing the existing script currently is. We could address the issues of the naming conventions in the mailmap file, but that assumes we stick with this approach. The bad part of using the mailmap is that we have to share/sync it separately.

A totally separate question I have is how we could use this to update the CITATION.cff and associate orcid for committers that have them. That is not for this issue.