Remote queries view using mock data

[charisk]

This changeset builds up an initial remote queries view based on some mock data. The view will gradually be refined and hooked into real data with further PRs.

See internal issue for more context.

Checklist

N/A: This is only relevant for remote queries, which is still an internal-only feature.

• CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
• Issues have been created for any UI or other user-facing changes made by this pull request.
• @github/docs-content-codeql has been cc'd in all issues for UI or other user-facing changes made by this pull request.

[shati-patel]

Hooray, thanks for doing this! Looking much nicer already 🖼️ 😄

I've left some minor comments so far, but it would be good to get another review too!

[aeisenberg]

Nice work.

[aeisenberg]

This looks awesome!

[sj]

Looks smashing! Can I suggest a tiny change of wording to "Summary: 13 repositories affected". It's quite common for users to write queries that are meant to explore a code base. For such queries, the term "affected" might sound a bit odd. And the number "13" is already mentioned in the text just above it.

So how about rewording "Summary: 13 repositories affected" to "Repositories with results (13)" or something like that? @nuthinking and @jf205 might have better ideas!

[charisk]

Looks smashing! Can I suggest a tiny change of wording to "Summary: 13 repositories affected". It's quite common for users to write queries that are meant to explore a code base. For such queries, the term "affected" might sound a bit odd. And the number "13" is already mentioned in the text just above it.

So how about rewording "Summary: 13 repositories affected" to "Repositories with results (13)" or something like that? @nuthinking and @jf205 might have better ideas!

Thanks @sj, I've gone ahead and made the change but we can also make further tweaks later on.

[nuthinking]

I know that we already show the number above in small but, also for consistency with the results header, I'd rather go for 13 repositories with results if affected is not generic enough.