Aim for the same rebar3 vsn across the board

[paulo-ferraz-oliveira]

My goal here is to remove a variable from potential CI processes.
I've had jobs fail in erlang:19:3 but not in erlang:23.1 due to rebar3 -specific issues (that we're left unsolved in previous versions, but not in the most recent ones).

[getong]

Sorry for the delay. I used to update the rebar3 version with the erlang version is updated, but if you do need to update all the rebar3 version, I am happy to merge it. Would you update the alpine directory rebar3 version and rebase your pr?

[paulo-ferraz-oliveira]

We need the update since this is failing on CI. Imagine running 19.3, 20.3, 21.3, 22.3, etc. and failing in 19.3 because of rebar3 (not the app or CI itself) 😄

What branch should I rebase this off of (or are you mentioning rebase in the sense of squash)?

[paulo-ferraz-oliveira]

@getong: I added bee9618 to change the alpine folders, master and README.md. It's now the same version from 19 to 23, the same versions rebar3 supports. Would you like further changes (or changes to existing ones)?