Create separate artifacts for JNI Library

[jmazanec15]

Currently, the ODFE RPM/DEB installation process copies the KNN JNI library from S3 in a preinstallation script. This has 2 problems:

1. Many users' clusters do not have access to the internet, so the preinstall script leads to an installation failure
2. Uploading the binary library to an S3 bucket will not scale and will not support versioning. It also is inelegant.

In order to fix these issues, it makes sense to ship the library as an independent DEB/RPM and have the KNN plugin depend on the library artifacts. Additionally, if a user's system configuration is incompatible with the binary library artifacts, we should provide an easy way to build the artifacts from source.