Materialized view vs. 8Knot query - repo_id

[JamesKunstle]

I'm getting DB read failures on my branch, and I rooted out the problem:

The materialized views for explorer_pr_assignments.sql and explorer_issue_assignments.sql have the line *.repo_id AS id, rather than *.repo_id as repo_id or otherwise, so the queries in 8Knot are failing, expecting to find a repo_id column.

Unclear whether the 8Knot queries need to adopt the 'id' column name or the materialized views should have the column be 'repo_id.'

[JamesKunstle]

Fix not necessary- materialized view conforms to other queries in app, just one step later than normal.