This creates a predictable password which would essentially function like a backdoor, except CA does not match passwords stored as MD5 hashes. Since the hash is not usable, creating this account has no purpose anyway.
Don't invoke application code when inserting H5P option
This invokes H5POptionObserver which then tries interacting with the cache, which might not be available at the time of running migrations. Additionally, migrations have to take the DB state up until the point it's ran into consideration, therefore it should not rely on application code which could change at any point.
Remove creation of useless default user
This creates a predictable password which would essentially function like a backdoor, except CA does not match passwords stored as MD5 hashes. Since the hash is not usable, creating this account has no purpose anyway.
Don't invoke application code when inserting H5P option
This invokes
H5POptionObserver
which then tries interacting with the cache, which might not be available at the time of running migrations. Additionally, migrations have to take the DB state up until the point it's ran into consideration, therefore it should not rely on application code which could change at any point.