Crossmark support

[bozana]

For OSS ORE project a Crossmark support is needed.
See https://www.crossref.org/documentation/crossmark/ and https://www.crossref.org/documentation/crossmark/participating-in-crossmark/.

See maybe also https://openjournaltheme.com/product/crossmark-plugin-ojs-3/ and https://forum.pkp.sfu.ca/t/crossmark-implementation-to-ojs/69271.

• The OSS ORE uses a DOI for each article version. We would need to decide if we would support Crossmark only in this situation, when a DOI is used for each article version, or if we would like to consider any other scenario described in examples here: https://www.crossref.org/documentation/register-maintain-records/maintaining-your-metadata/registering-updates/.
• crossmark section would needed to be added to the article registration with Crossref.
• A setting field for journal update policy would need to be defined and displayed on a web page that would need to have a DOI and be registered by Crossref, and added to all content (using the crossmark section). S.https://www.crossref.org/documentation/crossmark/crossmark-policy-page/.
• Crossref update types need to be considered: addendum, clarification, correction, corrigendum, erratum, expression_of_concern, ew_edition, new_version, partial_retraction, removal, retraction, withdrawal. (Closely related to Support version types and summaries #4860), s. https://www.crossref.org/documentation/crossmark/participating-in-crossmark/#00279.
• Crossmark button needs to be applied to the article landing page, HTML and PDF document.
• Adapt documentation (https://docs.pkp.sfu.ca/crossref-ojs-manual/en/crossmark)