Provide users with an easy setup experience in a variety of execution contexts

[MrPowers]

The jodie project will be used in a variety of different ways. Some users will like to include jodie as a dependency in their build.sbt file and others will want to attach the JAR file directly to a cluster. Here are some cases we'd like to handle:

• user adds jodie to their build.sbt file that specifies specific Delta Lake / Spark versions
• user attaches a JAR file to an existing cluster
• user adds jodie to their build.sbt file that specified a specific PySpark version, but doesn't have Delta Lake. The right Delta Lake version should be pulled in as a transitive dependency.

We should probably build an automated process that builds JAR files and attaches them to releases whenever a new release is created.

[brayanjuls]

user adds jodie to their build.sbt file that specified a specific PySpark version, but doesn't have Delta Lake. The right Delta Lake version should be pulled in as a transitive dependency.

Do you have a reference repo/doc where this is done?