Update seed-data script to use save data endpoint

[emmastephenson]

What needs to be done

Right now the seed script for the eCR Viewer manually saves data to the database, rather than using the endpoint on the eCR Viewer to do so. It needs to use the endpoint.

Why it needs to be done

In a deployed scenario, the eCR Viewer is the final phase of the pipeline - it saves both metadata and blob storage for future reading. Right now our seed script doesn't match this user pattern, and instead directly saves data to the database without using the Viewer's endpoint. Since the seed script is the backbone of our local development, this means we're not testing and using the application in the way our users will - which we need to fix.

Acceptance Criteria

• [ ] Orchestration configuration for seed-data is updated to call the eCR Viewer's save data endpoint directly
• [ ] There is NO manual writing to the SQL table in the seed script (excepting any database table setup). Only the Viewer's endpoints are used to interact with the database.

Technical Notes

Handy links:

• create-seed-data.py
• seed-ecr-viewer-config.json

[emmastephenson]

Considerations from Planning:

• May need to update orchestration service to handle eCR Viewer endpoint
• Need to think about how seed-data interacts with testing config/setup

[angelathe]

One more acceptance criteria - Need to remove extraneous schema definitions in 01-init.sql in this ticket (see link)

[angelathe]

Putting this back into the backlog - still blocked by 2367