Inconsistent behaviour when stats_persistent enabled and decryption fails

Add STATS_PERSISTENT=1 to the CREATE TABLE t1 statement in test innodb-bad-key-change2.test . The statement ALTER TABLE t1new RENAME TO t2new will pass making this test fail. Without stats_persistent it passes (ALTER TABLE t1new RENAME TO t2new fails as expected). There is overall problem when dealing with encrypted tables and decryption failures. Tables are in-always-check if decryption possible mode only if persistent stats are disable - because server needs to open a table to be able to calc the stats. With persistent stats enabled the tables will not be opened and some statements for tables that cannot be decrypted will succeed (for instant ALTER TABLE ... RENEW ...). This should be unified. The solution could be to identify those statements and make them succeed although decryption may fail for them or always open encrypted tables to see if they can be decrypted.