Update puma to latest. Be less conservative.

[jrafanie]

Puma does a pretty good job about following semantic versioning so it should be safe to update minor versions and will probably help us tackle the problems sooner rather than later.

https://github.com/puma/puma/blob/v4.2.1/History.md

• Depends on some UI team members 👍. It works for me but I didn't test puma:
  • with a debugger (tested by @himdel, thanks 🙇🙇🙇 )
  • consoles with websockets (tested by @skateman, thanks 🙇🙇🙇 )
  • action cable with notifications (tested by @skateman, thanks 🙇🙇🙇 )

[skateman]

Just to clarify, consoles are NOT using action cable 😉 only notifications. However, consoles are also running through websockets.

[skateman]

@miq-bot add_reviewer @skateman

[miq-bot]

Checked commit jrafanie@9806838 with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

[djberg96]

Do we have any sort of performance comparisons we can do? Just curious, I generally favor updating to the latest, especially since it seems like there have been a lot of fixes and updates since 3.7.

[himdel]

with a debugger

No issues with pry byebug, not noticing any issues with recompilation, ... LGTM IMO :)
(I didn't test actioncable or consoles.)

[skateman]

Both the notifications (AC) and the consoles work well.

[jrafanie]

@Fryguy this ready to go... thanks to @himdel and @skateman for testing the debugger, consoles, and notifications