Updating collection lock is required on `bundle install`

Problem

bundle install (and bundle update) requires rbs collection update when it updates Gemfile.lock about gems which have sig/. For example:

1. Install gem X v1.0.0 with bundler
2. rbs collection install
   • rbs_collection.lock.yaml has gem X entry with v1.0.0
3. bundle exec rbs validate or something
   • It works
4. Update gem X to v1.0.1 with bundler
   • Gemfile.lock is updated
5. bundle exec rbs validate or something
   • It doesn't work because rbs_collection.lock.yaml specifies gem X v1.0.0 but the version doesn't exist in the Bundler environment.
   • So we need to re-run rbs collection install to update rbs_collection.lock.yaml.

I think it is not a bug, but it takes time. Too strict I guess.

I can imagine this behavior will be a blocker of dependabot. For example:

1. Dependabot creates a PR to update gem X from v1.0.0 to v1.0.1
2. CI runs with rbs collection install --freeze and steep check
3. It fails because rbs_collection.lock.yaml has gem X v1.0.0 but actually v1.0.1 is installed.

Solution idea

Add an option to relax the version specification.
For example

• The configuration file has an option like prefer_gemfile_lock_version (the naming is tentative)
• If the option is enabled, rbs collection ignores version in rbs_collection.lock.yaml fi the source is rubygems. Then it uses versions in Gemfile.lock instaed.
• The problem is solved...?

I got feedback from @ybiquitous. Thanks!
https://twitter.com/ybiquitous/status/1438019865130848258

I guess your problem is the same as mine. If your problem is a different one, feel free comment to on this issue or create a new issue. Thanks.