Bump webpacker from 5.4.3 to 5.4.4

[dependabot]

Bumps webpacker from 5.4.3 to 5.4.4.

Changelog

Sourced from webpacker's changelog.

Please note that Webpacker 3.1.0 and 3.1.1 have some serious bugs so please consider using either 3.0.2 or 3.2.0

Please note that Webpacker 4.1.0 has an installer bug. Please use 4.2.0 or above

[6.0.0] - 2021-TBD

Please see UPGRADE GUIDE for more information.

• node_modules will no longer be compiled by default. This primarily fixes [rails issue #35501](rails/rails#35501) as well as numerous other webpacker issues. The disabled loader can still be required explicitly via:

const nodeModules = require('@rails/webpacker/rules/node_modules.js')
environment.loaders.append('nodeModules', nodeModules)

• If you have added environment.loaders.delete('nodeModules') to your environment.js, this must be removed or you will receive an error (Item nodeModules not found).
• extract_css option was removed. Webpacker will generate a separate application.css file for the default application pack, as supported by multiple files per entry introduced in 5.0.0. #2608. However, CSS will be inlined when the webpack-dev-server is used with hmr: true. JS package exports inliningCss. This is useful to enable HMR for React.
• Webpacker's wrapper to the splitChunks() API will now default runtimeChunk: 'single' which will help prevent potential issues when using multiple entry points per page #2708.
• Changes @babel/preset-env modules option to 'auto' per recommendation in the Babel docs #2709
• Adds experimental Yarn 2 support. Note you must manually set nodeLinker: node-modules in your .yarnrc.yml.
• Fixes dev server issues #2898
• Update static files path to from media/ to static/.

Breaking changes

• Renamed /bin/webpack to /bin/webpacker and /bin/webpack-dev-server to bin/webpacker-dev-server to avoid confusion with underlying webpack executables.
• Removed integration installers
• Splitchunks enabled by default
• CSS extraction enabled by default, except when devServer is configured and running

Commits

• 2a7e298 Release 5.4.4
• be0efe9 Merge pull request #3306 from amatsuda/5-x-exists
• 852949d ⛳
• d3606ff Use exist? instead of deprecated exists? (#3250)
• 061f33b Merge pull request #3305 from amatsuda/5-x-ci
• 1ec1ab3 Remove Travis CI (#2615)
• 004c97a Use latest RubyGems on Ruby >= 2.6
• dbf25e3 Let setup-ruby choose appropriate version of bundler
• 4c5d13a CHANGELOG: Add v5.4.3 release (#3162)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[mkllnk]

The changelog wasn't helpful here. This is a small patch (backport) release for compatibility with ruby 3.2. The main change is:

Use exist? instead of deprecated exists?

This should be safe. I'm merging.