Use spec file on Zenodo pipeline

[epassaro]

Description

• Use fixed spec file to avoid breakages in the Zenodo pipeline (notice this environment is not the tardis environment)
• Changes were already tested in the new tardis_zenodo CI workflow
• Fixes for .mailmap. Please be careful with the name and email address you commit from @marxwillia @KevinCawley

Motivation and context

Broken pipeline.

How has this been tested?

• Testing pipeline.
• Other.

Examples

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[codecov]

Codecov Report

Merging #1973 (0c50f0c) into master (b54dc86) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1973   +/-   ##
=======================================
  Coverage   59.85%   59.85%           
=======================================
  Files          70       70           
  Lines        8080     8080           
=======================================
  Hits         4836     4836           
  Misses       3244     3244           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[tardis-bot]

Before a pull request is accepted, it must meet the following criteria:

• Is the necessary information provided?
• Is this a duplicate PR?
  • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
  • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
• Does it pass existing tests and are new tests provided if required?
  • The test coverage should not decrease, and for new features should be close to 100%.
• Is the code tidy?
  • No unnecessary print lines or code comments.