Backport of 'Set GITLAB_BIN_DIR for Duo CLI and bump workflow image to v0.0.23' into 19.5

What does this MR do and why?

Backports !261515 (merged) to 19.5, together with !261473 (merged), which it was merged on top of. The other incident revert, !261482 (merged), is already on 19-5-stable-ee.

19-5-stable-ee currently ships DUO_CLI_VERSION = "9.29.0" without GITLAB_BIN_DIR. That is the combination that broke find_files in remote flows (rg is unavailable, EROFS on $HOME/.cache). This MR moves 19.5 to the same state as master:

• Default workflow image workflow-generic-image:v0.0.23 and DUO_CLI_VERSION = "9.30.0".
• GITLAB_BIN_DIR=/tmp/gitlab-bin in the sandbox job variables, refreshed on resume.

Duo CLI 9.30.0 also stops loading workspace MCP configuration (.gitlab/duo/mcp.json) for Rails-delivered flow runs: gitlab-org/editor-extensions/gitlab-lsp!4412 (merged).

Both commits are clean git cherry-pick -m1 picks. The net diff matches 261515 on master.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
• Required labels have been applied to this merge request
  • severity label and bug subtype labels (if applicable)
  • If this MR fixes a bug that affects customers, the customer label has been applied.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the E2E Omnibus GitLab EE pipeline (triggered by thee2e:test-on-omnibus-ee job) has succeeded. If it has failed (or shows warnings), investigate the failures. If you determine the failures are unrelated, you may proceed. If you need assistance investigating, request help in the #s_developer_experience Slack channel to confirm the failures are unrelated to the merge request.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).
• Once the backport has been merged, the commit changes will be automatically deployed to a release environment that can be used for manual validation. See after merging runbook for details.

References

• !261515 (merged)
• !261473 (merged)
• !261482 (merged)
• gitlab-org/editor-extensions/gitlab-lsp!4412 (merged)