Insert statements are generated for sequence tables after dropping in create-drop mode

[dzou]

An extra insert statement is generated for sequence tables after tables are dropped in create-drop mode. The statement ends up being a no-op and produces an extra error message.

Hibernate: START BATCH DDL
2021-03-12 18:36:13 INFO  access:47 - HHH10001501: Connection obtained from JdbcConnectionAccess [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess@50e649d5] for (non-JTA) DDL execution was not in auto-commit mode; the Connection 'local transaction' will be committed and the Connection will be set into auto-commit mode.
Hibernate: alter table Account_SubselectTest drop constraint FKfkf7s5uupggldl8xh30h8ysem
Hibernate: alter table AccountTransaction_SubselectTest drop constraint FK53ssmg9hbyxts0eqotd20jie5
Hibernate: drop table Account_SubselectTest
Hibernate: drop table AccountTransaction_SubselectTest
Hibernate: drop table client_subselect
Hibernate: drop table hibernate_sequence
Hibernate: RUN BATCH
Hibernate: INSERT INTO hibernate_sequence (next_val) VALUES(1)
2021-03-12 18:36:29 ERROR SchemaDropperImpl$DelayedDropActionImpl:547 - HHH000478: Unsuccessful: INSERT INTO hibernate_sequence (next_val) VALUES(1)