[ZEPPELIN-1605] zeppelin-interpreter: don't publish shaded JAR on maven central

[minahlee]

What is this PR for?

• Instead of creating fat jar for zeppelin-interpreter and add it to classpath, place zeppelin-interpreter.jar and dependencies under lib/interpreter directory and add this dir to classpath of zeppelin-server and interpreter. (removed maven-shade-plugin)
• Exclude some transitive dependencies from zeppelin-zengine which cause conflicts with those of zeppelin-interpreter
• Exclude configuration files(credential.json, notebook-authorization.json, shiro.ini) when create binary package.

What type of PR is it?

Improvement

What is the Jira issue?

ZEPPELIN-1605

How should this be tested?

1. Check if interpreter directory has created under zeppelin-distribution/target/zeppelin-0.7.0-SNAPSHOT/zeppelin-0.7.0-SNAPSHOT/
2. Test md interpreter works as expected after running below command:

$ mvn clean package -DskipTests -Pbuild-distr
$ cd zeppelin-distribution/target/zeppelin-0.7.0-SNAPSHOT/zeppelin-0.7.0-SNAPSHOT
$ ./bin/zeppelin-daemon.sh start

3. Check if md intepreter process has zeppelin-distribution/target/zeppelin-0.7.0-SNAPSHOT/zeppelin-0.7.0-SNAPSHOT/lib/interpreter/* in it's classpath.

Questions:

• Does the licenses files need update? no
• Is there breaking changes for older versions? no
• Does this needs documentation? no

[bzz]

@minahlee Looks great to me!

Could you please rebase on latest master? It looks like there are a few conflicts now

I assume that for testing, it should be enough to build mvn clean package -Pbuild-distr -DskipTests and make sure Zeppelin run from zeppelin-distribution/target is able to execute a paragraph, or is there a better way?

[minahlee]

@bzz Thank you for review, I just rebased. And yes, the way you described is correct way to test this PR, I updated it in description.

[bzz]

Sounds awesome, thank you!

Let's merge then, if there is no further discussion.