enhancement/readme-and-changelog-update

[PaulDalek]

Updated README, CHANGELOG and Puppeteer version.

[jszuminski]

LGTM!

[bvogel]

Question: the README now mentions "The v4 introduces numerous breaking changes", however the CHANGELOG only has New Features, Enhancements and Fixes. Could the CHANGELOG please clearly mark what changes are breaking?

[bvogel]

After reading the CHANGELOG several times, are these the breaking changes:

- Changed the customCode section of options to customLogic in order to avoid confusion with the existing customCode property within.
- Renamed the environment variables for a better representation of their roles (refer to all envs in the README's Environment Variables section).
- Renamed the HIGHCHARTS_MODULES and HIGHCHARTS_INDICATORS environment variables respectively to HIGHCHARTS_MODULE_SCRIPTS and HIGHCHARTS_INDICATOR_SCRIPTS.
- Renamed the scripts property of the config options to customScripts.
- Renamed the initPool function to initExport in the main module.
- Renamed the init function to initPool in the pool module.
- Renamed the environment variable POOL_LISTEN_TO_PROCESS_EXITS to OTHER_LISTEN_TO_PROCESS_EXITS.
- Moved the listenToProcessExits from the pool to the other section of the options.

If so, I don't think many users will be affected, however they should be their own section in the changelog?

[PaulDalek]

@bvogel Most of the breaking changes relate to name changing of some properties and envs, yes. But there are also many others included in the CHANGELOG.

I don't think many users will be affected

Probably but some might be, therefore the info.

[bvogel]

As we a currently affected by #523 in our production system - how far away are we from a new (beta/rc) release? If there is no immediate time planed we might want to look to use the current master/main branch as gem (which we really don't want to do...)