[Gandiva][Java] Safeguard jvm before loading the gandiva library

Today we load the gandiva library always when trying to use the jni bridge, but we have run into issues causing the jvm to crash in untested paths.

Proposal is to do load the library in a separate process first and if it works only then load in the current process.

This would be done only once at startup/first load.

**Reporter**: [Praveen Kumar](https://issues.apache.org/jira/browse/ARROW-4003) / @praveenbingo

_{**Note**: *This issue was originally created as [ARROW-4003](https://issues.apache.org/jira/browse/ARROW-4003). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

先追蹤 Java JNI 橋接的首次程式庫載入路徑，以及目前啟動或首次載入時的初始化運作方式。實作提議的獨立程序載入檢查，只有在檢查成功後才在目前程序中載入，並確保該檢查只執行一次；驗證在失敗或不受支援的路徑上 JVM 仍然安全。

由索引模型根據 Issue 內容生成。