Test fix for BK packaging failure

[dliappis]

Proposed commit message

PR #38952 surfaced a bug with #38366 where
the parameters weren't enclosed in doublet quotes.

Failed logs: https://buildkite.com/elastic/beats-xpack-osquerybeat/builds/1973#018f06dd-19fd-40e0-ba21-960d195f178e/131-316

Related issues

• Osquerybeat: Strip osqueryd binary for linux #38952
• Disable buildvcs within docker #38366

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @dliappis? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-04-23T15:22:34.776+0000

• Duration: 11 min 20 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[alexsapran]

/test packaging-linux

[dliappis]

closed as the issue was resolved via https://github.com/elastic/ci-agent-images/pull/640