[jloux-brapi]

Description

Story: BI-2923

• On creation of BrAPI Observation Variables for traits they are now associated with the brapi program
• The general fetch used by the cache now retrieves observation variables by program instead of exref.

Dependencies

• brapi-java-prodserver: feature/BI-2923
• brapi: feature/BI-2923

Testing

• Create New Ontology terms in DeltaBreed, verify the terms are created and show up on the Ontology Page
• Update ontology terms in DeltaBreed. This can be achieved by clicking Show Details and then clicking Edit, where if they are not already used you can edit some elements of the term. Activating and Deactivating also updates ontology. Simplify verify the changes are reflected once they are made.

Checklist:

• I have performed a self-review of my own code
• I have tested my code and ensured it meets the acceptance criteria of the story
• I have create/modified unit and/or integration tests to cover this change or tests are not applicable
• I have commented my code, particularly in hard-to-understand areas
• I have either updated the source of truth or arranged for update with product owner if needed https://breedinginsight.atlassian.net/wiki/spaces/BI/pages/1559953409/Source+of+Truth

[humsika]

since traits are now fetched only by programDbId, any variable with a NULL program_id will trigger the throw at line 211 for the whole program. The only way I can see that happening is if the ProdServer migration runs first and the old bi-api creates a trait before this version is deployed. Will these three PRs always be deployed together? If not, it might be worth falling back to the exref lookup for any trait IDs missing from the result.