Handle or warn about trying to install appmap with bundler in deployment mode

Running command: `ruby --version`

ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin22]


Running command: `gem env home`

/Users/aleksandrcuvakov/.asdf/installs/ruby/2.4.0/lib/ruby/gems/2.4.0


Running command: `bundle check --dry-run`

The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.
The Gemfile's dependencies are satisfied


Running command: `bundle config get without`



Running command: `bundle install`

You are trying to install in deployment mode after changing
your Gemfile. Run `bundle install` elsewhere and add the
updated Gemfile.lock to version control.

If this is a development machine, remove the
/Users/aleksandrcuvakov/Documents/DEV/clubup/Gemfile freeze
by running `bundle install --no-deployment`.

The dependencies in your gemfile changed

You have added to the Gemfile:
* appmap

The report names Gemfile, Gemfile.lock, and the Bundler commands bundle check --dry-run and bundle install. Reproduce the failure with appmap added to a deployment-mode bundle, then locate the installation entry point that invokes Bundler. Done should mean the deployment-mode case is handled or produces a clear warning without leaving the dependency state ambiguous.