Regression: Google BigQuery connector loses Native SQL Query UI on gear icon click

Hello Power BI Team,

Following the recent updates and the rollout of the new BigQuery connector implementation (ADBC), the Power Query UI is experiencing a significant regression regarding the Value.NativeQuery step.

Previously, clicking the gear icon on the "Source" step of a BigQuery connection opened a dialog box clearly displaying the Native SQL Statement, allowing for easy copying, pasting, and formatting. Now, this UI is completely missing or fails to map for BigQuery connections.

As a BI Architect, this severely disrupts the workflow. Instead of a clean SQL text box (which is still perfectly functional and stable in the SQL Server connector), we are forced to use the Advanced Editor. This exposes the raw M code, wrapping the SQL in double quotes and converting all line breaks to #(lf), making it extremely tedious to copy/paste the query directly to BigQuery Studio for testing without manual text parsing.

The SQL Server connector handles NativeQuery UI mapping flawlessly. The BigQuery connector needs to maintain this same parity and stability.

Steps to Reproduce:

• Step 1: Connect to Google BigQuery and input a Native SQL query via Advanced Options.
• Step 2: Apply the step, then click the gear icon on the "Source" step to edit the SQL.
• Step 3: Notice the UI no longer provides the clean SQL input box.

Please investigate and restore the Native Query UI parsing for BigQuery connections.