feature: added github action for checking .zenodo.json formatting

[lettlini]

This is a draft Github action that checks the formatting of .zenodo.json.

• Have you followed our guidelines in CONTRIBUTING.md?
• Have you self-reviewed your code and corrected any misspellings?
• Have you written documentation that is easy to understand?
• Have you written descriptive commit messages?
• Have you added NumPy docstrings for newly added functions?
• Have you formatted your code using black?
• If you have introduced a new functionality, have you added adequate unit tests?
• Have all tests passed in your local clone?
• If you have introduced a new functionality, have you added an example notebook?
• Have you kept your pull request small and limited so that it is easy to review?
• Have the newest changes from this branch been merged?

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (fa7a194) 54.60% compared to head (1bc805b) 54.60%.

Additional details and impacted files

@@            Coverage Diff             @@
##           RC_v1.5.0     #292   +/-   ##
==========================================
  Coverage      54.60%   54.60%           
==========================================
  Files             15       15           
  Lines           3170     3170           
==========================================
  Hits            1731     1731           
  Misses          1439     1439           

Flag	Coverage Δ
unittests	54.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[w-k-jones]

Looks good! Codecov test failed during the result upload, so I've re-run and it should be fine

edit: missed that this is still in draft, please request re-review if needed

[freemansw1]

Neat! This resolves #178