feat(csharp): BigQueryPerformance changes

[alokdeorani]

This change focuses on performance and metadata handling.

Key changes include:

Metadata Query Support: The driver now supports standard
ADBC metadata retrieval functions. This allows you to query for catalogs (projects), schemas (datasets), tables, columns, and primary keys.
This is much faster than querying InformationSchema.

Automatic Large Query Handling: The driver now performs a "dry run" before executing a query. If it estimates that the query will process a large amount of data (over 120MB), it automatically enables settings to handle large results, improving performance and reliability for big queries.
New Configuration Parameters: Several new parameters have been added to control these new features, such as adbc.bigquery.include_public_project_id and parameters for metadata commands.
Testing Updates: The testing framework has been updated to validate the new metadata functionality.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[CurtHagenlocher]

Thanks! Feedback left.

[CurtHagenlocher]

In principle, shouldn't BigQueryConnection.GetTableSchemas and BigQueryConnection.GetObjects also be changed to use the more efficient implementations instead of querying INFORMATION_SCHEMA? This could be filed as a followup work item.

[CurtHagenlocher]

Thanks! My comments are mostly nitpicking, but we should probably think a little harder about returning the schema for nested structured data because it will be hard to fix this later without breaking existing uses.

Edit: there are also a few linter errors from the build.

[CurtHagenlocher]

Thanks! The changes look good but the linter is still complaining. I think it's mostly about lines with trailing white space. One way to fix those in VS is to open the file and use Control-K Control-D to autoformat. (You can also do it manually of course.)

[alokdeorani]

Thanks! The changes look good but the linter is still complaining. I think it's mostly about lines with trailing white space. One way to fix those in VS is to open the file and use Control-K Control-D to autoformat. (You can also do it manually of course.)

Thanks for the review, I did as suggested. I'm hoping it should be without errors now.

[CurtHagenlocher]

@alokdeorani, should I assume that you closed this PR by accident?

[alokdeorani]

@alokdeorani, should I assume that you closed this PR by accident?

Yeah I think I did by mistake.

[CurtHagenlocher]

The linter is still failing :(. I think it's because my previous advice about autoformat doesn't work for trailing whitespace in comments. I guess autoformat probably doesn't touch comments.

[alokdeorani]

The linter is still failing :(. I think it's because my previous advice about autoformat doesn't work for trailing whitespace in comments. I guess autoformat probably doesn't touch comments.

Checking

[alokdeorani]

The linter is still failing :(. I think it's because my previous advice about autoformat doesn't work for trailing whitespace in comments. I guess autoformat probably doesn't touch comments.

Checking

I did some more fixes. I hope this time it will work.

[CurtHagenlocher]

I did some more fixes. I hope this time it will work.

Almost there! It looks like BigQueryStatement.cs either has an extra newline at the end or is missing a newline at the end.

[alokdeorani]

I did some more fixes. I hope this time it will work.

Almost there! It looks like BigQueryStatement.cs either has an extra newline at the end or is missing a newline at the end.

Fixed it