Replace ad hoc synonym type "layperson" with OMO:0003003

[cthoyt]

Closes #10140

@matentzn can you help me update the configuration to properly import the OMO term?

[matentzn]

I have seen this but there are right now a lot of competing priorities, sorry. While this PR is 100% correct and part of our overall vision, this needs a bit more careful thinking around communication. I have my eyes on it.

[pnrobinson]

What exactly is OMO and what advantage is this for us? I am concerned about keeping things easy to use for curators and users, and having our own definition of plain-language term seems reasonable since what is a layperson will differ according to context and surely any software using this will know all about HPO?

[matentzn]

@pnrobinson there is no advantage for HPO; but also not a big disadvantage. The advantage is for cross-ontology integration. We want to be able to query for layperson synonyms of terms across ontologies (say MONDO, MAXO, HPO, Uberon etc) using a single standardised query. OMO is a vocabulary for ontology metadata properties where we standardise all properties used across all ontologies - we have already done a lot of this in HPO in the past year, these are just the last pieces of that process.

[pnrobinson]

I am going to close this for now. If anybody needs this, it is trivial to map the current lay person label. I think we need to keep the file as simple as possible and only add things that are not immediately obvious (e.g., an URI) if there is a real need.