GH-49651: [C++][FlightRPC] Fix ODBC Linux test segmentation fault

[alinaliBQ]

Rationale for this change

GH-49651

What changes are included in this PR?

Pass ARROW_TEST_LINKAGE: "static" to Linux ODBC tests.
Update CMakeLists.txt to enable static test linkage on Linux.

Note: enabling Linux test build will be in a separate PR

Are these changes tested?

Tested on local machine and in our local repository

Are there any user-facing changes?

N/A

• GitHub Issue: [C++][FlightRPC][ODBC] Use static test linkage for Linux ODBC #49651

[github-actions]

⚠️ GitHub issue #49651 has been automatically assigned in GitHub to PR creator.

[alinaliBQ]

@lidavidm @kou This PR is ready for review, please have a look

[lidavidm]

Hmm, why are there two copies of gRPC in the first place?

[alinaliBQ]

Hmm, why are there two copies of gRPC in the first place?

My understanding is, the arrow_flight_sql_odbc_shared has a copy of gRPC, and the tests have a copy of gRPC because it uses gRPC to set up the mock server. So when we dynamically link the tests to the shared ODBC lib, we end up with 2 copies.

[lidavidm]

So then arrow_flight_sql_odbc_shared (or the tests) is currently always statically linking gRPC? Because if they both dynamically link gRPC, there should be no problem.

[alinaliBQ]

So then arrow_flight_sql_odbc_shared (or the tests) is currently always statically linking gRPC? Because if they both dynamically link gRPC, there should be no problem.

Yes, arrow_flight_sql_odbc_shared is statically linked with gRPC on macOS from #49219. This enables the ODBC .dylib to act as a self-contained library without needing additional third party dependencies. And due to macOS Excel's sandboxed environment, ODBC .dylib files are usually statically linked to dependencies in order to be successfully loaded.