Trait Ontology Definitions: move from conf file to cvprop table

[dwaring87]

There are a number of places where the trait_ontology_db_name config key is used and treated like it can only be a single value. I think it would be good to check that it is being correctly parsed as though it could have multiple values.

Also, this begs the question: is the only way to add a second trait ontology by manually inserting a row into cvprop? Perhaps there should be a way to make updates between sgn_local.conf and cvprop coherent?

Alternatively, maybe the places that use trait_ontology_db_name need to be shifted away from using the config and instead rely on cvprop for the actual identities of the trait ontolgies

Originally posted by @ryan-preble in #6015 (review)

[dwaring87]

There are also trait_ontology_cv_name and trait_ontology_cvterm_name keys which seem to only be used by the BrAPI endpoints?

[dwaring87]

trait_variable_onto_root_namespaces (which can be a list) does not seem to be used anywhere

[dwaring87]

Something that I realized while looking at #6044 : the trait designer assumes only one trait ontology for autocompleting names and showing the embedded ontology browser. Same for downloading the trait ontology - would need to be changed to download multiple ontologies, either in series or all at once. This is potentially a bit of a breaking change