Actually i have just found another solution in the related Jira https://hibernate.atlassian.net/browse/HHH-11699.

The property below did the trick for me.
spring.jpa.properties.hibernate.id.new_generator_mappings: true

So technically the issue is fixed, but probably it still exists in "old" generator mappings.