CI housekeeping

[kianmeng]

This PR bumps the action/checkout and Rebar3 versions in the GitHub CI workflow file.

I still retain the legacy OTP as I'm not sure this project wants to adhere to erlang/rebar3#2555 of only support the latest three OTP versions?

[wojtekmach]

Thank you!

[wojtekmach]

Regarding supporting ancient OTP versions, if dropping some would help rebar, I'm open to that.

[kianmeng]

Regarding supporting ancient OTP versions, if dropping some would help rebar, I'm open to that.

Not sure about this, best to check with Rebar3 developer, I just passed by this repo. ;-)

Out of curiousity, from what I have gathered so far, checking the significant public projects (not sure if there are inhouse private projects) that depends on hex_core, from https://hex.pm/packages?search=depends%3Ahexpm%3Ahex_core

There are the top three by downloads:

• https://hex.pm/packages/rebar3_hex (>=OTP 25)
• https://hex.pm/packages/rebar3_depup (>= OTP 24)
• https:/wojtekmach/req_hex (Elixir 1.11 or OTP >= 21)

Using the Erlang/OTP 25 as the baseline version could offer a compelling combination of advantages of streamlined CI pipeline, enhance security, boost performance, and use new features?

[kianmeng]

🥳 🥳 🥳 🥳 🥳