Establish series/0.2 against sjs-dom 2.x

[armanbilge]

This establishes http4s-dom series/0.2 which will publish against scala-js-dom 2.x. It will also add support for Scala 3.1.

If anyone feels strongly about a strategy like #15 instead of branching, feel free to make a proposal. I'm not sure it's worth the complexity, and it would be different than what http4s proper and http4s-jdk-http-client are doing.

Instead, my proposal is we do all new feature development on this branch (if anyone wants to work on that!) and only do bug/security fixes for series/0.1 if they come up.

Most of the major scalajs projects are moving to sjs-dom 2.x anyway:

• Update to scalajs-dom 2.0.0 com-lihaoyi/scalatags#225
• Update scalajs-dom to 2.0.0 japgolly/scalajs-react#998
• Update to sjs-dom 2.0.0 final shadaj/slinky#511
• Update to sjs-dom 2.0.0 final raquo/scala-dom-types#72
• update scalajs-dom to 2.0.0 ScalablyTyped/Converter#377

[armanbilge]

I'm going to move forward with this, nothing controversial here, just a dependency update.

[rpiaggio]

Sorry for the delay, we've been swamped these past few weeks.

I have no strong feelings about using projectmatrix but I must say I like the idea more each day. Anyway, we are already branching here and LGTM.

[armanbilge]

Thanks, we can always switch to project matrix at a later time as well. But whenever I do the mental math, using project matrix here only makes sense if:

• there is development on series 0.1, and
• this happens more than X times, where X is enough times that merging a branch is annoying :)

Actually I'll be happy to be wrong about this, if it means people are actively developing and using this lib 😆