Make query constraints for access paths query configurable

[koesie10]

This makes the query constraints for the access paths query configurable since these can differ between the languages. It also updates the query constraint for the Ruby query from the access-path-suggestions tag to access-paths, since that is how the query was merged into CodeQL main.

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.

[shati-patel]

Makes sense! 🚢

I guess this just means that we temporarily can't use the access paths query in the extension? (Since the "old" version used a different tag, and this new version doesn't have the correct output format for now)

[koesie10]

I guess this just means that we temporarily can't use the access paths query in the extension? (Since the "old" version used a different tag, and this new version doesn't have the correct output format for now)

Yes, but you'd have to have manually added the "old" query to your workspace, so the access path queries were probably not working for the majority of people anyway. You should still be able to use the old query by changing the access-path-suggestions tag to access-paths and not updating the CodeQL submodule to main. After #3320 is merged, you'd then need to remove the old query and update the submodule (or copy the new query).