Use dynamic schema names rather than hardcoded ones

[dbeatty10]

resolves #223

Problem

There can be permissions errors if different database users are trying to modify the same hardcoded schema.

This can be the case if there are two different CI systems running at the same time (as is the case currently with CircleCI (legacy) and GitHub Actions (new)).

Solution

Remove schemas that are completely hardcoded and use a schema name based on target.schema instead.

Changing the upstream table changed the expected output slightly, and I updated the expectation to match. I think this is okay, especially since I didn't change the logic of any macros -- I only changed the upstream model definitions and the downstream expected output.

Checklist

• This code is associated with an issue which has been triaged and [accepted for development]