Add CodeMeta JSON-LD Context File

[matthewfeickert]

Description

As part of an IRIS-HEP initiative to improve the citation quality/ease for all software it has been recommended by @danielskatz that projects:

• Track authors/contributors to software as it is developed
• Create a citation metadata file in the software repo and keep it up to date
• Link Github and Zenodo to get DOIs for major releases
• In the README and docs clearly says how to cite the software

pyhf already does all of this, as:

• There is an AUTHORS file as well as a listing of the authors in the docs
• There is a .zenodo.json that formats Zenodo with the correct metadata and adds the ORCID of the authors
• There is a Zenodo DOI that is kept in sync with our release schedule (almost) fully automatically (almost as it requires 1 button click).
• There is a Citation section in both the README and the docs webpage with the preferred citation

It has been pointed out though that we should also look into adding a CodeMeta Project JSON-LD Context File as with it

zenodo will read [it] and will be basically the same as schema.org so that this will help google index software, and tools be able to use the metadata file in softwareheritage.org to automatically build a citation for a particular commit.

(cc @gordonwatts as this might be of interest)

[matthewfeickert]

As an example, the parsl library has a codemeta.json file.

[danielskatz]

tools to generate CodeMeta files are in https://codemeta.github.io/tools/

[matthewfeickert]

While it doesn't look to be very actively developed, it should be possible to add a GHA workflow to use codemetapy to automatically update the codemeta.json on release merges in the same way that we run bumpversion.