Session.go assumes schema format by appending "-audio" or "-video" during query

[JamKelley22]

Problem:

While --video_schema and --audio_schema name can be anything when running run_backfill.py there is an underlying assumption that "-audio" and "-video" are on the end of the schema name. run_backfill.py does not automatically append them when running the containers.

Impact:

After successfully inserting videoframes or audioframes into a session, the query to retrieve them is not as expected or impossible to form. If the original schema appended "-audio" or "-video" (eg. schema: "edusense-audio") then only using the first part of the schema will succeed. If the original schema did not append this then the frames are not queryable (eg. schema: "0.1.0" transforms to "0.1.0-audio").

Solution:

In storage/query/resolver/session.go lines 123 and 165 need to have the second argument updated to remove the string concatenation.

Side effects:

Any arguments automatically passed into scripts like run_backfill.py will need to be updated to match the fully qualified expected schema.