dev-call, show-ast - Use the same quarto binary as the one used to run the command

[cderv]

This change is using quartoConfig.cliPath() to get the quarto binary to use to be the same the one quarto dev-call was run.

Otherwise, the quarto use could be the one on PATH, which can be different that the one used (dev version vs released version if both installed), and also on windows we need quarto.exe or quarto.cmd depending on which is used. quarto on PATH won't always work without the extension.

and why we have this function for example
https://github.com/quarto-dev/quarto-cli/blob/fd54213c3e3f5fa929f6669b9ffb41547954f31c/tests/utils.ts#L192-L197

Opening the PR so that this is traced, and also for you to check this is ok to use that on Mac too.

[posit-snyk-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[cscheid]

That's exactly correct, thank you. I now also reviewed the rest of our codebase for instances of "quarto" or 'quarto'. I think that after this fix, we use it correctly everywhere, although we have some lua duplication. In astpipeline.lua, we build the path correctly, but manually.

[cscheid]

👍

[cderv]

In astpipeline.lua, we build the path correctly, but manually.

Oh interesting. We have a param for filter that we should probably use.

quarto-cli/src/resources/pandoc/datadir/init.lua

Lines 999 to 1000 in 6e36833

	config = {
	cli_path = function() return param('quarto-cli-path', nil) end,

I'll do another PR