start/daemon not returning when include_erts is true

[SebCav]

Hi,
when I build a release with include_erts set to true, I can run my project with "<path to start script> daemon", but the script never returns. This does not happen when I comment out the include_erts.
I reproduced this on a simple project created with "rebar3 new app test", both on a Debian and on an Arch linux, only common thing is OTP19.3 (from esl deb's on the Debian, custom built on Arch).

[SebCav]

I tracked down my problem to be linked to #853
Before running the post-start hooks, there's an rpc call for erlang:is_alive which fails for the same reason as the above issue

[tsloughter]

Pretty sure we decided not to support 19.x anymore but I do need to verify this is the case and make it clear because I see some tests still run against it so that certainly makes it look like to the user that they can expect 19 to work.

[SebCav]

When I opened this issue the documentation at https://www.rebar3.org/docs/getting-started/ stated that last five versions were supported, from OTP-23 to OTP-19. I see the page changed in May so your documentation is already up to date, it is this issue that is outdated.

[SebCav]

Maybe it could be useful if you could tag rebar3 versions when you change the OTP support, so one can choose properly which one to use. I don't know if it's me but I do not see an easy way to pick the last tag supporting e.g. OTP19.