fix: migrate describeTableQuery and showIndexesQuery to TS

[WikiRik]

Pull Request Checklist

• Have you added new tests to prevent regressions?
• If a documentation update is necessary, have you opened a PR to the documentation repository?
• Did you update the typescript typings accordingly (if applicable)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Does the name of your PR follow our conventions?

Description Of Change

This PR builds on the new extractTableDetails to provide a cleaner describeTableQuery function. Schemas are now tested for all dialects. There is one behaviour change since the previous PR, which is that the schema is only used in the query when it's not the defaultSchema of the dialect. I would like that to be a choice we make throughout the codebase consistently. That is in line with the changes to quoteTable

It also migrates showIndexesQuery with a new test for the above mentioned behaviour of quoteTable.
It also adds that test to dropTableQuery and adds the proper infix for the quoteIdentifier test file name.

[WikiRik]

@ephys could you already take a look at this before I do the same approach for some other queryGenerator functions?

[WikiRik]

I'm not sure if I fixed the failing postgres test correctly, but according to the withSchema docs it will place a schema in front. So it's strange that it didn't pick this up before. Maybe because the schema is not always specified anymore for postgres (it had a fallback to public before)?

[WikiRik]

I haven't migrated dropTableQuery to TS yet since it uses rejectInvalidOptions. I think it's a separate PR on how to deal with that

[ephys]

I need to make further improvements to describeTable to be able to use it in the tests of #14687.
It's very likely that I'll drop the schema option in a follow-up PR, so I don't know about adding the deprecation notice

[WikiRik]

I need to make further improvements to describeTable to be able to use it in the tests of #14687. It's very likely that I'll drop the schema option in a follow-up PR, so I don't know about adding the deprecation notice

Let's still deprecate it here (but move it to describeTable), and you can remove it in a different PR if you know for sure that you'll drop it

[WikiRik]

I think we should be good for this PR.

Future PRs are;

• Updating quoteTable so it always returns a schema. See fix: migrate describeTableQuery and showIndexesQuery to TS #15299 (comment)
• Removing the default schema workaround USER from DB2 and CURRENT SCHEMA from ibmi once we know the wanted schema. (USER might be a default schema for DB2, but it requires some further investigation)
• Discuss how to migrate methods that use rejectInvalidOptions. (preferably in a way that we do not need both a Set with possible options and the type)

[ephys]

Thanks :)