[AE-664] Add Provide tag for libhdfs to resolve yum dependency check

The major point of this is to add the Provide tag for libhdfs since it doesn't exist, and for 3rd party application such as Impala or others may require this as part of the RPM. By adding these to the fpm command, we will be able to install impala via yum and pull in the dependent RPM without manually running rpm commands.
After digging more into rpmbuild, I notice that whenever you include a binary to the final result, it will always bring in those libs as part of the Required. It turns out that rpmbuild will use ldd command to derive what is required and try to pull those 'files' as a dependency. We can use "AutoReqProv" to disable this, however, I believe that the root cause came from vcc-hadoop where the RPM didn't specify these files generated in the %files macro, otherwise, these tags should be automatically included in the vcc-hadoop RPM. I would suggest we create a RPM spec for vcc-hadoop or look into how fpm incorporates the 'ldd' so it aligns with rpmbuild and produce the same behavior and results.

[impala122@impala scripts]$ ldd ~/rpmbuild/BUILDROOT/usr/bin/impalad 
	linux-vdso.so.1 =>  (0x00007fff8a35d000)
	libjsig.so => /usr/java/default/jre/lib/amd64/libjsig.so (0x00007f46e42fd000)
	libboost_thread-mt.so.1.46.1 => /usr/local/lib/libboost_thread-mt.so.1.46.1 (0x00007f46e40e4000)
	libboost_regex-mt.so.1.46.1 => /usr/local/lib/libboost_regex-mt.so.1.46.1 (0x00007f46e3dfd000)
	libboost_system-mt.so.1.46.1 => /usr/local/lib/libboost_system-mt.so.1.46.1 (0x00007f46e3bfa000)
	libboost_filesystem-mt.so.1.46.1 => /usr/local/lib/libboost_filesystem-mt.so.1.46.1 (0x00007f46e39db000)
	libdl.so.2 => /lib64/libdl.so.2 (0x0000003e07c00000)
	libjvm.so => /usr/java/default/jre/lib/amd64/server/libjvm.so (0x00007f46e2b6b000)
	libhdfs.so.0.0.0 => /opt/hadoop/lib/native/libhdfs.so.0.0.0 (0x00007f46e295d000)
	libevent-1.4.so.2 => /usr/lib64/libevent-1.4.so.2 (0x00007f46e2742000)
	libz.so.1 => /lib64/libz.so.1 (0x0000003e08000000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x0000003e09c00000)
	librt.so.1 => /lib64/librt.so.1 (0x0000003e08400000)
	libboost_date_time-mt.so.1.46.1 => /usr/local/lib/libboost_date_time-mt.so.1.46.1 (0x00007f46e252e000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003e07800000)
	libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003e0e400000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003e09000000)
	libm.so.6 => /lib64/libm.so.6 (0x0000003e08800000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003e0a000000)
	libc.so.6 => /lib64/libc.so.6 (0x0000003e07400000)
	/lib64/ld-linux-x86-64.so.2 (0x0000003e07000000)
	libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x0000003e0d800000)
	libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f46e2312000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003e09400000)
	libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000003e0cc00000)
	libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000003e0d000000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003e0bc00000)
	libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000003e0d400000)
	libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000003e0e000000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003e0dc00000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003e08c00000)