Disabling QLTY_FEATURE_RUBY_BINARY_INSTALL is needed to fix some installs

[brynary]

What happened?

For at least two reported users, they had to set our QLTY_FEATURE_RUBY_BINARY_INSTALL feature flag to off to get Ruby to install.

What did you expect to happen?

Either the install should succeed (ideal), or if we can run a pre-flight check to determine the binary install won't work, then we could early exit with a warning. We could potentially fallback from binary install to source install automatically.

Can you reproduce the problem?

Only sometimes

CLI Version

qlty 0.463.0 macos-arm64 (893403d 2024-12-19)

Relevant log output