SNOW-2184600: Reduce binary size by opt-out `arrow-go/compute` package

[datdao]

What is the current behavior?

The gosnowflake SDK uses the apache/arrow-go/compute package to support batch downloads. However, including this package significantly increases the final binary size (by ~14MB). In use cases like mine, where the SDK is used only to query system tables and perform DDL operations, the batch processing functionality provided by compute is not needed.

What is the desired behavior?

Introduce a build tag (e.g., tag nobatch) or other mechanism to allow clients to exclude the arrow compute dependency when it's not required for their use case.

How would this improve gosnowflake?

Adding such a build tag would enable more lightweight builds of applications using gosnowflake. This is particularly beneficial for distributing binaries in environments where size matters like CLI Migration tools

[sfc-gh-dszmolka]

thank you @datdao for raising this improvement request. The team will consider when planning for future enhancements for the Go driver.
To help prioritize (also others who are interested, i see a couple of thumbs ups!) amongst other requests - kindly reach out to your Snowflake Sales Representative and let them know of your use-case, and that you would need such feature. Thank you in advance!

[sfc-gh-pfus]

@datdao how did you calculate this 18MB?

[datdao]

@sfc-gh-pfus, this is a minimal setup to reproduce the issue.
https://github.com/datdao/snowflake-sdk-debug

[datdao]

package main

import (
	_ "github.com/snowflakedb/gosnowflake"
)

func main() {}

Simply importing it causes the built binary to grow by ~30MB

[sfc-gh-pfus]

I know this driver is huge (we have making it lighter in our backlog), but I'm wondering how did you come up to this 18MB. This 30MB is related to the code required only by init functions and that's fair, probably running any query gives another megabytes, but how did you find this exact 18MB by arrow compute module?

[sfc-gh-pfus]

Ok, I see the point. I briefly verified your PR and did the following tests:

1. I compiled select1.go on master branch and the executable is 36MB.
2. When compiled the same but on your branch with nobatcch the executable is 20MB.
   Good direction!
   We are going to release v2 in the next couple of months, I think it would be a good time to reorganize code. I'll let you know if we will follow your approach or maybe use some other approach.

Thank you!