fix #1344 (bundle exec startup without RUBYOPT present)

[bughit]

No description provided.

[stereobooster]

Related #1344

UPD Need to do better investigation before merging this

[bughit]

@stereobooster
the investigation is here: #1344 (comment)

[bughit]

@stereobooster @nateberkopec

My investigation (#1344 (comment)) showed that in a bundle exec puma invocation if puma resolves to a ruby script rather than say a bash rbenv shim, then this puma ruby script will be loaded in process and Bundler::ORIGINAL_ENV["RUBYOPT"] will not be set. In fact nothing set by the following will be in ORIGINAL_ENV

def set_bundle_environment
      set_bundle_variables
      set_path
      set_rubyopt
      set_rubylib
end

Is that not sufficient to proceed with the fix? Or are there other expectations/assumptions for what's in ORIGINAL_ENV than need to be dealt with?

[nateberkopec]

Closing in favor of #1385