Ensure the logFileLocation is set

[aeisenberg]

logFileLocation was not set after a query finishes running. I don't know when this bug was introduced. I think it goes as far back as the refactor to remove the old query server.

Replace this with a description of the changes your pull request makes.

Checklist

• 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.

[angelapwen]

I think the code scanning warning can be dismissed as the line in question is not actually assigning a value.

[aeisenberg]

Thanks for the review. Still need to add a change note.

[aeisenberg]

The code scanning warning was legitimate since there was a value being assigned in the constructor parameter list as well as the constructor body. I refactored a bit so there is no warning.

[angelapwen]

The code scanning warning was legitimate since there was a value being assigned in the constructor parameter list as well as the constructor body. I refactored a bit so there is no warning.

Ah I see.. I think the location it showed up on was a bit misleading (because it didn't show on any assignment). Thanks!