fix(bq_driver): Prevent crash when listing datasets for invalid projects

[Anshu6250]

This PR resolves an issue where the driver would crash when encountering invalid or inaccessible project IDs configured via the "Additional Projects" DSN setting.

[shivamd-gpartner]

please document the code here

[sachinpro]

@shivamd-gpartner @Anshu6250 Is this change still valid?

[sachinpro]

A few questions:

1. If invalid additional project is provided, is the driver throwing an error or crashing?
2. If an error is sent, what is the error message and for what API?
3. In case of crash, it cannot be happening at the client SDK level. So we need to fix the client library or the driver.

We will not be introducing any extra validations which impact performance to fix a crash.

[Anshu6250]

A few questions:

1. If invalid additional project is provided, is the driver throwing an error or crashing?
2. If an error is sent, what is the error message and for what API?
3. In case of crash, it cannot be happening at the client SDK level. So we need to fix the client library or the driver.

We will not be introducing any extra validations which impact performance to fix a crash.

1. The driver is throwing an error, not crashing. The trace logs demonstrate that the driver gracefully catches the invalid project and exits the API call, returning a standard -1 (SQL_ERROR) code to the calling host application.

2. The error is thrown during the SQLTablesW API call. The exact diagnostic error message sent is:
   [HY000] [Google][ODBC BigQuery Driver] [BigQuery] Permanent error, with a last message of Not found: Project anshu (404)