[improve] Upgrade RoaringBitmap to 1.6.6 version

[lhotari]

Motivation

There have been improvements and bug fixes in RoaringBitmap since 1.2.0 version. We haven't been able to upgrade since the artifact hasn't been published to maven central for a while. RoaringBitmap is now available in maven central with coordinates org.roaringbitmap:roaringbitmap this has changed from the previous org.roaringbitmap:RoaringBitmap dependency. Pulsar users using pulsar-client-original without shading might need to pay attention to this detail if they are depending on org.roaringbitmap:RoaringBitmap directly since that would cause 2 versions of the library on the classpath simultaneously. Either one would be used.

Modifications

• upgrade RoaringBitmap to 1.6.6 version

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

[lhotari]

Let's wait for RoaringBitmap/RoaringBitmap#824

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.59%. Comparing base (436ca72) to head (19128c9).

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #25253      +/-   ##
============================================
- Coverage     72.75%   72.59%   -0.16%     
+ Complexity    34068    33888     -180     
============================================
  Files          1959     1959              
  Lines        155401   155401              
  Branches      17724    17724              
============================================
- Hits         113062   112818     -244     
- Misses        33364    33590     +226     
- Partials       8975     8993      +18     

Flag	Coverage Δ
inttests	25.64% <ø> (-0.32%)	⬇️
systests	22.35% <ø> (-0.10%)	⬇️
unittests	73.55% <ø> (-0.17%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 74 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.