Fix message parsing + data saving for condition info

What needs to be done

Update the message parsing and data saving on the non-integrated viewer to properly save condition and rule summary information. It's currently stored as a block of text in the database, but should instead be saved as new rows.

Specifically, you'll need to:

Update the message_parser schema to extract all RR information (you may be able to look at the fhirPath.yml for the paths)
Update database saving to store both condition and rule summary info to new rows

Why it needs to be done

Utility for us:

This will make it much easier to display conditions on the eCR Library and to filter by condition

Utility for our end users:

Condition is probably the #1 way our users will try to group or process eCR data - it's important to get it right.

Acceptance Criteria

[ ] Message parser returns a list or JSON object with all the conditions and rule summaries (not concatenated) - see below
[ ] Saving condition and rule summary information works on Postgres with the core schema - [ ] Saving condition and rule summary information works on SQLServer with the core schema - [ ] Saving condition and rule summary information works on Postgres with the extended schema
[ ] Saving condition and rule summary information works on SQLServer with the extended schema

Technical Notes

Owned by eng team - write out any important technical considerations such as: architecture plan/notes, data dependencies, testing plan, etc. Also link any tickets that are dependent on or related to this task

rr: {
 conditions: [
    // name, fhir path, other metadata per condition
        rule summaries: [
        // name, description, etc for each rule summary 
        ]
     ]
}

Conditions and rule_summaries are both lists of objects. Rule_summaries are nested inside/associated with a specific condition.

Additional context

Related to both #2235 and #2694.

CDCgov / phdi