add permissible values to InstrumentVendorEnum and InstrumentModelEnum for sequencing applications

[aclum]

This PR expands on the two enumerations to support sequencing based vendors and models.

We will need to write migration code to map existing values of instrument_name to vendor and model.

[turbomam]

This is an excellent enumeration PR. Thanks for the thorough annotation with OBI terms. Was it a pain to pick them all out? @cmungall and I have some ideas for providing some automation.

If there's one single exact_mapping for a permissible value, it would be better to express it as the meaning of the PV. mappings are textual annotations but meanings are structural. If the schema or the data are converted to RDF, the meanings can be queried for subclasses, superclasses, and other grouping axioms.

If that's OK with you, it could be quickly accomplished with

s/exact_mappings:\n +- /meaning: /

[aclum]

@turbomam This was a bit painful b/c you can't see the actual term IDs in the tree view. Probably would have been better to dump this and use some of the ontology tools but I'm not very familiar with those. It would be useful to have a little script that could make a permissible value out of every child of a term (in this case a good starting point would have been to make a term for all the children of OBI:0400103, then delete the ones we don't need).