This bug has now been fixed and released. It is included in Neo4j version 2025.03.0, which is available for download from the deployment center (https://neo4j.com/deployment-center/), and it is also the current version on Aura (https://console.neo4j.io/).