Add ENVO-OEO mapping-file

[LillyG901]

Summary of the discussion

See #2010

The goal of this PR is to add a SSSOM file that includes previously via anotation property skos:closeMatch matched terms from ENVO.
The match-type has been reassessed and often changed to skos:exactMatch. For the reasons of this change please check this table.

Type of change (CHANGELOG.md)

Add

• envo-oeo sssom file

Workflow checklist

Automation

Closes #

PR-Assignee

• 🐙 Follow the Pull Request Workflow
• 📝 Update the CHANGELOG.md
• 📙 Add #'s to term tracker annotation

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[LillyG901]

@stap-m To fully close #2010 we would have to change/remove the preexisting mappings via annotation property. Should this be handled in a separate PR or should I also do this here?
Also would you prefer I remove them alltogether or should I just replace the skos:closeMatch with skos:exactMatch for all terms where we decided to change it?

[cthoyt]

hi @stap-m @LillyG901, I just talked with Mirjam and will prepare a demo using https://github.com/cthoyt/sssom-curator/ for predicting and curating such mappings between ENVO-OEO (and potentially other external ontologies)

[cthoyt]

FYI, that demo is in biopragmatics/biomappings#241