Exclude certain Bundler settings when composing bundle

[vinistock]

Motivation

Closes #2440, closes #3196

Certain Bundler settings are better used only when the user is in control, like deciding when to package gems or if Bundler should automatically install binstubs for all gems.

This PR starts ignoring certain settings from the composed environment.

Implementation

Added a list of ignored settings that we reject before building the environment that we'll use to run bundle install/update.

Automated Tests

Added tests for both bundle bin and bundle package related settings.

[vinistock]

• Exclude certain Bundler settings when composing bundle #3277 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label graphite-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Merge activity

• Mar 7, 12:57 PM EST: A user added this pull request to the Graphite merge queue.
• Mar 7, 1:24 PM EST: A user merged this pull request with the Graphite merge queue.

[andyw8]

Following up to this, I noticed that Bundler has a BUNDLE_IGNORE_CONFIG option:

Executing bundle with the BUNDLE_IGNORE_CONFIG environment variable set will cause it to ignore all configuration.

Would this be helpful? Are there any configuration values that we do want to preserve?

[agrobbin]

@vinistock is there something that needs to be done to ensure this takes effect? I upgraded to v0.9.8 as soon as it was released, but am still seeing these gem package files show up in vendor/cache.

[vinistock]

v0.9.8 is the extension version, but the bug fix is in the server gem. Since this fix is in the LSP launcher, doing gem update ruby-lsp for the Ruby version you are using should probably do the trick.

Running ruby-lsp --version should display v0.23.12.

[agrobbin]

Hmm, I'm on v0.23.12 and am unfortunately still seeing these files get added to vendor/cache.

[vinistock]

Indeed. I double-checked and I think #3342 will fix it.