Statically linking arrayfire

Right now arrayfire has to be used by linking to the DLL. Since the only parts of arrayfire that are included in the Rust bindings are BSD 3-clause, there should be no problem statically linking arrayfire. Is it possible that we could choose whether or not arrayfire is statically linked to ease distribution? Also, is there any downside to just always statically linking arrayfire? I feel like that would be more in-line with what the Rust community expects: adding a crate to your `Cargo.toml` should "just work".

Start with the Cargo.toml integration and the current DLL-based ArrayFire linking setup. Investigate how the Rust bindings select and distribute the native library, including the tradeoffs of optional versus always-static linking. Done means the supported linking choice and its distribution implications are documented and implemented or clearly scoped.

由索引模型根据 Issue 内容生成。