Fixes #23962 - Fix Style/ExpandPathArguments cop

Fixes #23677 - Add additional config options to foreman-debug

Allows for full control of upload behaviour of foreman-debug via the
config file. The following new variables are introduced: UPLOAD_URL,
UPLOAD_CMD, UPLOAD_USAGE_MSG, UPLOAD_UNSET_MSG, UPLOAD_SUCCESS_MSG,...

Fixes #23643 - Stop bundle install in Travis

Since 90db5e364ff209f093c64849e21d3362644367f8 we no longer require core
Foreman in script/plugin_webpack_directories.rb which means we no longer
need all dependencies installed. Just Ruby with JSON support. This...

Fixes #23511 - Generate webpack plugins in context of vendor/bundle

Fixes #23414 - Allow plugins to compile in production

Fixes #23361 - Handle webpack manifests from plugins

In a production setup Foreman can't write to the manifest.json location.
Here we copy the pattern from the above sprockets initialization and
change the webpack-rails setting to read it. Because webpack-rails...

Refs #23147 - Fix style offences

Fixes #23147 - Allow plugins to compile production webpack assets

Refs #23215 - 2.3 compat. for webpack in plugins script

.match? was only introduced on 2.4, therefore it's failing to run
on 2.3 and test pipelines for plugins with webpack & Ruby 2.3 fail

Fixes #23215 - Keep original names in webpack bundle

Currently the webpack config is shortening the name of the js bundles
for plugins. E.g, foreman_remote_execution becomes remoteexecution, and
so on.
This becomes hard to deal with when we want to figure out which plugin...