chore: update sttp to v4

[agilesteel]

I also took the liberty to update the sbt and Scala versions.

[agilesteel]

Ah I didn't see #416.

[kubukoz]

Should we rename the package to org.polyvariant.sttp4.oauth2(...), so that (similarly to sttp itself) it doesn't clash with older versions? On the other hand, I doubt this is used a lot transitively, so having multiple sttp versions on the classpath may not be a likely concern...

[kubukoz]

please bump sbt-github-actions and regenerate CI, recent runner changes / actions changes must've broken the build. Latest is https://github.com/sbt/sbt-github-actions/releases/tag/v0.25.0 (now published under the com.github.sbt org)

[kubukoz]

if you'd like, that can be a separate PR. After that (or any other PR) is merged we won't have to approve every CI run from you :)

[agilesteel]

Bumped.

[agilesteel]

Should we rename the package to org.polyvariant.sttp4.oauth2(...), so that (similarly to sttp itself) it doesn't clash with older versions? On the other hand, I doubt this is used a lot transitively, so having multiple sttp versions on the classpath may not be a likely concern...

I don't think it's necessary but I can do it if you like. Should I?

[kubukoz]

Should we rename the package to org.polyvariant.sttp4.oauth2(...), so that (similarly to sttp itself) it doesn't clash with older versions? On the other hand, I doubt this is used a lot transitively, so having multiple sttp versions on the classpath may not be a likely concern...

I don't think it's necessary but I can do it if you like. Should I?

I asked @majk-p and we both think it's ok to keep the current state (don't repackage) - let's just resolve CI then

[majk-p]

Thanks for the contribution @agilesteel 💪

[agilesteel]

Thanks for the contribution @agilesteel 💪

Any time. I hope I didn't break anything 🙏🏼