MDEV-35748 : Attempting to create a CONNECT engine Table results in n…

[janlindstrom]

…on-InnoDB sequences in Galera cluster error

• The Jira issue number for this PR is: MDEV-35748

Description

Problem was incorrect condition on wsrep_check_sequence when ENGINE!=InnoDB.

Fix is not use DB_TYPE_XXX because it is not correct on dynamic storage engines. Instead used storage engine name is looked from thd->lex->m_sql_cmd->option_storage_engine_name.

For CREATE TABLE allow anyting except ENGINE=SEQUENCE.
For CREATE SEQUENCE only ENGINE=InnoDB is supported.
For ALTER TABLE if original table contains sequence information only ENGINE=InnoDB is supported.

Release Notes

TODO: What should the release notes say about this change?
Include any changed system variables, status variables or behaviour. Optionally list any https://mariadb.com/kb/ pages that need changing.

How can this PR be tested?

TODO: modify the automated test suite to verify that the PR causes MariaDB to behave as intended.
Consult the documentation on "Writing good test cases".

If the changes are not amenable to automated testing, please explain why not and carefully describe how to test manually.

Basing the PR against the correct MariaDB version

• This is a new feature or a refactoring, and the PR is based against the main branch.
• [ x] This is a bug fix, and the PR is based against the earliest maintained branch in which the bug can be reproduced.

PR quality check

• [x ] I checked the CODING_STANDARDS.md file and my PR conforms to this where appropriate.
• [x ] For any trivial modifications to the PR, I am ok with the reviewer making the changes themselves.