mima check on pull requests

[pjfanning]

• relates to =core Make use of statefulMap instead of statefulMapConcat. #311
• I don't know for definite but that PR looks like the removed method should cause a mima failure

[He-Pin]

I ran the mimaReportBinaryIssues locally and it work.

[He-Pin]

better to have a dedicated binary-compatibility-checks workflow like pekko

[mdedetrich]

Can we also please make a decision on https://lists.apache.org/thread/4oymvkv6t415pocdtc6l1vxssoflbw9f and apache/pekko#532 ? The whole point of that thread/PR is to actually implement a proper handling of MiMa that sticks to semver and actually automatically deals with changes where people add functionality (doing MiMa checks against a hardcoded Pekko 1.0.0/1.1.0 is not enough, we should actually be doing MiMa checks against the latest release of the software against every PR).

I understand the solution may not be the cleanest (although tbh we kind of have our hands tied due to ASF process) but what I am suggesting is standard and normal in Scala OS projects, its not some crazy out there idea (otherwise this feature in dynver wouldn't even exist).