Don't report extended fields as additional fields in versionedRelease

[duncandewhurst]

Data which includes both versioned releases and extensions results in the data review tool flagging additional fields in the versioned releases.

From @kindly: it isn't possible for publishers to include versioned-release patches in their extensions because

if you applied multiple extensions that have versioned-release patches the composite output would not be correct in some cases. The only way to get correct output would be to merge the release schemas first and then apply the versioning so it would only work if you only had a single extension.

you would not patch the versioned release schema you would run https://github.com/open-contracting/standard/blob/4aec59865bc6401b017ab0b68a9536405879216e/standard/schema/utils/make_versioned_release_schema.py on the rhe patched release schema however that is not done by cove and potentially could be done.

cc @yolile

[jpmckinney]

In the very short term, we can also not report additional fields on versioned releases.

[duncandewhurst]

CoVE: Add support for extended versioned release data

[jpmckinney]

Seems to be fixed. http://standard.open-contracting.org/review/?source_url=https://raw.githubusercontent.com/open-contracting/sample-data/main/fictional-example/1.1/record/ocds-213czf-000-00001-withversions.json

[jpmckinney]

Nevermind - the DRT doesn't report OCDS fields as additional (like in #84), but it will report extended fields as additional.

[jpmckinney]

As mentioned in issue description, can be easily fixed by moving code that converts release schema to versioned schema from standard repo to ocdsextensionregistry, and then calling it in the SchemaOCDS.registry method.