Update DB Schemas [Attempt 2]

[lprzychodzien]

Resolves #229

Explanation

Updated schema to align with issue discussion. With sagerx being the production user-facing schema

Tests

1. What testing did you do?

• deleted all postgres data
• tore down postgres config with docker-compose down --volumes
• Repulled all data

testing logs

``` ```

[jrlegrand]

I had to resolve a merge conflict in staging/rxnorm_historical/rxnorm_historical__ndcs.sql weirdly - I just made it like how it is in the main branch. Other than that, it's still putting all the stg/int/marts in sagerx_dev aside from the pg_stat_statments tables which end up in sagerx. I'm still not clear how / when / why we switch over to the sagerx schema for "production" stuff. But simply having everything (aside from datasources) in one schema is a step forward in my opinion.

I ran the marts through to completion to make sure they worked - looks like they do.

sagerx schema

sagerx_dev schema

sagerx_lake schema