Hypersistentence Optimizer reports an issue marked as blocker

Expected behavior

No issues should be listed as blocker.

Actual behavior

When analysis application with Hypersisitance Optimizer, it points out the following:
BLOCKER - PooledSequenceOptimizerEvent - You should set the [hibernate.id.new_generator_mappings] configuration property to the value of [true], as Hibernate can then use the pooled or pooled-lo identifier optimizers for sequence-based entity identifiers. Note that the pooled and pooled-lo optimizers are not backward compatible with the legacy hilo optimizer that you might have used with Hibernate ORM 3 or 4. So, if you were using the hilo optimizer, then you would need to increase the current sequence number so that is greater than any previously allocated entity identifiers. For more info about this event, check out this User Guide link - https://vladmihalcea.com/hypersistence-optimizer/docs/user-guide/#PooledSequenceOptimizerEvent

Steps to reproduce behavior

Run analysis with Hypersisitance Optimizer against a application test that uses SportBootTest that application

Start by reviewing the reproduction described in the issue: a Spring Boot test analyzed with Hypersistence Optimizer and the PooledSequenceOptimizerEvent reported as BLOCKER. Check open pull request #2220 for the current work; done means the analysis no longer reports this finding as a blocker.