CODECHECK metadata collects addtional links

Authors and/or codecheckers can provide URLs (ideally DOIs) related to data and code as named links, which are then also shown in the sidebar of the article landing page:

- GitHub/Lab links (`repository` in the codecheck.yml)
- [Binder-ready](https://mybinder.readthedocs.io/en/latest/introduction.html) repository links or a "notebook link" (to be added to codecheck.yml)
- Dataset DOI, etc. (different repo providers) (to be added to codecheck.yml)

_Will need to update the `codecheck.yml` to reflect this with a list of named/typed links._ > https://github.com/codecheckers/discussion/issues/3#issuecomment-3213714782

--------

**User story:**

- _As a researcher, I want to easily find and reuse the verified code and data, so that I can use it for my own scientific work and build upon it._
---

## Related User Stories

- **R-SC3** (direct): As a reader, I want the article's landing page to provide structured, direct links to the verified code repository...
- C-MM1 (related): As a codechecker, I want the plugin to provide a form that generates, validates, and stores the codecheck.yml...
- R-SC1 (related): As a reader, I want to see a CODECHECK summary, the certificate ID, and links...
- P-IM1 (related): As a journal manager, I want to enter, edit, and view CODECHECK metadata entirely within the OJS editorial workflow...

_User story references from the [CHECK-PUB User Stories document](https://codecheck.org.uk/pub/)._