Make the "Create query" location workspace-specific

[shati-patel]

If a user picks a folder in which to create custom queries (createQuery.qlPackLocation), that should be saved in workspace settings, rather than global settings by default. See internal linked issue for details! 📦

I've also changed createQuery.autogenerateQlPacks to get written to workspace settings, for consistency. There's no harm either way, but I think we should default to workspace settings, and only write to global settings for "higher-level" settings (such as enabling/disabling telemetry) ⚙

Checklist

N/A—this is still feature-flagged 🎁

• 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.
• [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

[robertbrignull]

LGTM

Us I understand it, if a value has already been written the global settings, then we'll continue to use it. But if we write a new value it'll go to workspace settings. So in that way it's compatible with existing data and that's good.

[shati-patel]

As I understand it, if a value has already been written the global settings, then we'll continue to use it. But if we write a new value it'll go to workspace settings. So in that way it's compatible with existing data and that's good.

That's exactly right! Thanks ✨