separate out the uberjar profile so that the bits that control the
classpath are in a separate profile (now called "release") which can
be more easily brought in separately during development to test, without
being forced to build an uberjar to test
remove the uberjar alias, which only was added because i did not
realize that leiningen by default automatically does a clean before
building a jar (???)