ZH-267 - Add approach on Zenodo and DOI minting

[M-casado]

Summary

Added a section to the accessioning documentation explaining the integration with Zenodo for automatic release DOI minting

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New content (non-breaking change which adds new content)
• [x] Modified content (non-breaking change which modifies existing content)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Motivation and Context

Once implemented, it will help with the persistent identification of SOP releases.

References

ZenHub 267

Changes Introduced

• Added section to SOP accessioning document

Review

Not yet reviewed. I tested it with a few personal repositories and my own Zenodo account. The configuration with GDI's Zenodo account is still pending, but they were notified already.

Additional Notes

NA

Checklist:

General Compliance:

• [x] My changes follow the code style of this project (GDI SOP Style Guide) and the file naming conventions of the file accessioning proposal.
• [x] I have verified that all new updated content is accessible, including checking that all external references are readable (i.e., no broken links). These may include references to external resources that should be resolvable, and internal references among SOPs.

Only applicable if the PR includes new, or changes to, GDI SOPs (i.e., documents at sops/):

• [ ] My SOP-related changes adhere to the Generic SOP Template, including format and required fields.
• [ ] I have consulted the Charter, ISM, and ORR documents to ensure compliance.
• [ ] I am complying with the established procedure for SOP creations and modifications, including respecting review phases and notifying needed contributors for reviews.

[M-casado]

Thanks for the reviews, guys.