WIP: [#2187] MessageAudit modernization and performance optimization

[mattrpav]

• AtomicBitArrayBin provides lock-free bin array for storing messageIds
• ConcurrentMessageAudit demonstrates a MessageAudit using JDK-only concurrent hashmap
• CaffeineMessageAudit demonstrates a MessageAudit using Caffeine cache library
• MessageAuditPerformanceTest compares results between the implementations
• activmeq-client/src/test/resources/benchmark-results.html provides results of a test run on MacBookPro M3

[cshannon]

CaffeineMessageAudit is not going to work without some tweaks as it isn't entirely thread safe. The map updates (adding/removing) from the cache would be ok but it doesn't protect another thread from removing or update after you get an object from the cache.

For example in your rollback method:

    var bab = cache.getIfPresent(pid.toString());
    // At this point another thread could remove/update the entry in the cache
    if (bab != null) {
        bab.setBit(id.getProducerSequenceId(), false);
    }

[cshannon]

Also, from first glance the AtomicBitArrayBin class looks incredibly complex, did you use something to generate that? I have a lot of hesitation with introducing something that complicated vs simply locking without a real benefit. simple locking may be better under high contention anyways (that's where the benchmarking comes into play)

The main issue here is verifying it's actually correct and truly thread safe and won't introduce weird bugs