[C-API] Avoid C++ includes from arrow.h when including c_api.h

[desertstsung]

I've got the similar problem like #6839, while compling my C code. According to the issue, I found out that Ten0/lightgbm-rs@243322e is a good solution, but not so robust, so I made this fix.

[desertstsung]

@desertstsung please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

[jameslamb]

Thanks for your interest in LightGBM.

@Ten0 @borchero could you help review this?

[desertstsung]

Sorry for clicking Re-request review by accident.

[jameslamb]

/AzurePipelines run

[StrikerRUS]

/AzurePipelines run

[StrikerRUS]

/AzurePipelines run

[StrikerRUS]

/AzurePipelines run

[borchero]

I honestly don't know if this is the most ergonomic way to do this since I have too little experience with C(++) codebases 😅 as long as it works, I don't oppose it though

[desertstsung]

An SSL error? I don't understand why this happened🧐

[jameslamb]

There are hundreds of network requests made for each run of LightGBM CI. It's rare but not THAT rare for some of them to fail due to temporary network disruptions. I've retriggered the failed jobs, we should expect them to pass.

Very very very unlikely those failures were related to your changes here.

[desertstsung]

Ah I see. Thank you

[jameslamb]

Thanks very much for the contribution!

I think we should have a smoke test in this repo compiling a small C program linking to lib_lightgbm.so and using its C API. That'd help catch things like this in the future and give us more confidence in solutions like this one.

That's tracked in #4609

But with all other CI passing here, I think this is safe to merge. Thanks very much for the contribution, we'd love to have you come contribute more in the future!

[desertstsung]

I think we should have a smoke test in this repo compiling a small C program linking to lib_lightgbm.so and using its C API.

I agree that we should have a smoke test written in pure C and exercises the C API. I’ll work on this when I have some free time.

Thanks as well for keeping an eye on this PR!