fix the GPU flavor problem for Scala

[lanking520]

Description

Currently the pom file configuration did not correctly find the libcuda name as well as path problems to fetch the libmxnet.so.
@frankfliu @zachgk @piyushghai @andrewfayres

Reference:

ldd -r libmxnet.so
	linux-vdso.so.1 =>  (0x00007ffffd3eb000)
	libcudart.so.9.2 => /home/ubuntu/mxnet/staticdeps/usr/local/cuda-9.2/lib64/libcudart.so.9.2 (0x00007f7c126d5000)
	libcublas.so.9.2 => /home/ubuntu/mxnet/staticdeps/usr/local/cuda-9.2/lib64/libcublas.so.9.2 (0x00007f7c0e907000)
	libcurand.so.9.2 => /home/ubuntu/mxnet/staticdeps/usr/local/cuda-9.2/lib64/libcurand.so.9.2 (0x00007f7c0a9c9000)
	libcusolver.so.9.2 => /home/ubuntu/mxnet/staticdeps/usr/local/cuda-9.2/lib64/libcusolver.so.9.2 (0x00007f7c03588000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7c03380000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7c0317c000)
	libgfortran.so.3 => /home/ubuntu/deploytest2/lib/./libgfortran.so.3 (0x00007f7c02e55000)
	libcufft.so.9.2 => /home/ubuntu/mxnet/staticdeps/usr/local/cuda-9.2/lib64/libcufft.so.9.2 (0x00007f7bfd7fb000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f7bfd4e5000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7bfd1df000)
	libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 (0x00007f7bfcfb0000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f7bfcd9a000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7bfcb7c000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7bfc7b3000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f7c3e2e1000)
	libquadmath.so.0 => /home/ubuntu/deploytest2/lib/./libquadmath.so.0 (0x00007f7bfc573000)

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
• Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
• Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
• Code is well-documented:
• For user-facing API changes, API doc string has been updated.
• For new C++ functions in header files, their functionalities and arguments are documented.
• For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
• Check the API doc at http:https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
• To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

[stu1130]

@mxnet-label-bot add [pr-awaiting-review]

[frankfliu]

LGTM

[piyushghai]

LGTM