I am attempting to upgrade Neo4j in a deployment from 5.12.0 to 5.14.0, and when I do, the password is not being set from the secret created in the deployment (neo4j-auth.yaml). This was not an issue with 5.12.0 as this secret was reliably set as the password and could be used to login to the server. I need the password to work upon deployment, so resetting the password by turning auth_enabled off (to reset the password) and on again is not a workable solution. Is there something in the helm charts from this upgrade that changes this behavior or handling of the secret? I've looked at all the commits, and nothing jumps out to me as a red flag.