[NU-1094] Cats Effect 3 bump

[lciolecki]

Describe your changes

• bumped Cats Effect to version 3
• refactoring
• improved FlinkTestMainSpec
• improved benchmarks

Benchmarks

Before

[info] Benchmark                                                                     Mode  Cnt        Score       Error  Units
[info] p.t.n.e.b.interpreter.ManyParamsInterpreterBenchmark.benchmarkAsync          thrpt   25   164289.415 ±  3444.184  ops/s
[info] p.t.n.e.b.interpreter.ManyParamsInterpreterBenchmark.benchmarkSync           thrpt   25   258857.290 ±  7074.453  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkFutureAsync      thrpt   25    91131.231 ±   899.709  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkFutureSync       thrpt   25  2317693.965 ± 73199.850  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkAsyncIO          thrpt   25   147976.146 ±  8215.637  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkSyncIO           thrpt   25  1392072.271 ± 16367.403  ops/s
[info] p.t.n.e.b.aggregate.AggregatorBenchamark.sumAggregatorAdd                     avgt   25        0.024 ±     0.001  us/op
[info] p.t.n.e.b.spel.SampleSpelBenchmark.benchmark                                  avgt   25        0.048 ±     0.001  us/op
[info] p.t.n.e.b.suggester.ExpressionSuggesterBenchmark.chainCallBenchmark             ss    5      101.173 ±    11.743  ms/op
[info] p.t.n.e.b.suggester.ExpressionSuggesterBenchmark.complexExpressionBenchmark     ss    5     1401.843 ±   278.441  ms/op

After

[info] Benchmark                                                                        Mode  Cnt        Score        Error  Units
[info] p.t.n.e.b.interpreter.ManyParamsInterpreterBenchmark.benchmarkAsyncService      thrpt   25   238584.487 ±   2240.850  ops/s
[info] p.t.n.e.b.interpreter.ManyParamsInterpreterBenchmark.benchmarkSyncService       thrpt   25   240782.340 ±   4590.133  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkFutureAsyncService  thrpt   25   106851.712 ±   2253.305  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkFutureSyncService   thrpt   25  1552035.161 ± 102814.218  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkIOAsyncService      thrpt   25   102889.543 ±    294.573  ops/s
[info] p.t.n.e.b.interpreter.OneParamInterpreterBenchmark.benchmarkIOSyncService       thrpt   25   964319.320 ±   6763.407  ops/s
[info] p.t.n.e.b.aggregate.AggregatorBenchamark.sumAggregatorAdd                        avgt   25        0.024 ±      0.001  us/op
[info] p.t.n.e.b.spel.SampleSpelBenchmark.benchmark                                     avgt   25        0.049 ±      0.001  us/op
[info] p.t.n.e.b.suggester.ExpressionSuggesterBenchmark.chainCallBenchmark                ss    5       97.300 ±      9.947  ms/op
[info] p.t.n.e.b.suggester.ExpressionSuggesterBenchmark.complexExpressionBenchmark        ss    5     1209.948 ±     65.236  ms/op

Checklist before merge

• Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• Code is cleaned from temporary changes and commented out lines
• Parts of the code that are not easy to understand are documented in the code
• Changes are covered by automated tests
• Showcase in dev-application.conf added to demonstrate the feature
• Documentation added or updated
• Added entry in Changelog.md describing the change from the perspective of a public distribution user
• Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• Verify that PR will be squashed during merge

[coutoPL]

I think I managed to fix the problem found by FlinkTestMainSpec. Currently, this test is for the useIOMonadInInterpreter = true case. IMO it'd be nice to run the test with useIOMonadInInterpreter = false too. It seems that this case implementation was broken (now, it is fixed too).

[piotrp]

@lciolecki can you recheck performance after these changes?

[coutoPL]

Based on the code of benchmarks we have, I think the previous implementation I pushed is not correct. It looks like we don't have good tests that cover the functionality we touch in this PR. Moreover, it looks like FlinkTestMainSpec needs some love too. Let me work on this for a while ...

[raphaelsolarski]

Good job!
I leaved a few minor comments.

Please, squash before merge 😄

Piotr is absent. His comments were addressed.