What needs to be done

Write a backend query to find all unique conditions for all eCRs stored in the Viewer.

Why it needs to be done

This is one of the backend prerequisites to making filters work on the frontend (see ticket #2751). To populate the condition filter dropdown, we need to know all the conditions that a user could filter by.

Acceptance Criteria

• Backend query available to gather all unique conditions across our eCR storage
  • Query works for core schema
  • Query works for extended schema
• Endpoint so that frontend can use this query should also be included

Technical Notes

First in a series of sorting tickets - actually using this query will come later.

Additional context

We thought about having a separate "conditions" table that would be the master list of all conditions available, but there are two issues with this approach:

1. It's another table for our partner STLTs to maintain
2. Each eCR store won't actually have the full contingent of potential conditions - it depends on what they've authored in RCKMS.