Add CommandGetXdbcTypeInfo to Flight SQL Server

[c-thiel]

Which issue does this PR close?

Closes #4054

[tustvold]

This looks sensible to me, but I'm not very familiar with this area of the codebase. Perhaps @alamb or @avantgardnerio might be able to take look

[alamb]

Thank you @c-thiel

CI is not passing on this PR due to a few more places needing an update. Here is a PR to your branch that should get them working: c-thiel#1

[c-thiel]

Before we merge, I noticed that the same method is also missing for the client. I am adding it as well.

[c-thiel]

@alamb / @avantgardnerio :
I am missing another quite similar function - currently a do_get with cmd arrow.flight.protocol.sql.CommandStatementQuery executes the do_get_fallback method of the server. This is not caught in the match.

Should I add a new PR or do you prefer to extend this?

Edit: NVM, I had a buggy ODBC driver. CommandStatementQuery should never be in a do_get.

[c-thiel]

Actually, this deserves a separate issue.

[avantgardnerio]

NVM, I had a buggy ODBC driver

This is why I think integration testing is almost as important as manually trying to interpret the spec. IMO we should try stuff with the JDBC / ODBC drivers, record what happens, then try to mimic those tests with the Rust client and add them to the test suite.

I wouldn't want to merge the change that breaks something about JDBC that others are actively using.

In the case of CommandStatementQuery specifically, I wouldn't be surprised if that isn't working properly, since I've only been testing with JDBC and that driver always seems to turn everything into a prepared statement, even if on the Java side the user asks for an un-prepared statement.

[alamb]

IMO we should try stuff with the JDBC / ODBC drivers, record what happens

I agree -- I think this testing is covered by #2409. I agree it would be a fantastic addition