Use pure applescript to open the target application

Using a shell script appears to be unnecessary and just adds complexity.

One possible issue with this approach is whether any applications depend
on environment information from the shell, but such issues would
probably arise when opening applications normally. The only application
I'm currently aware of with issues like this is Atom with the Go plugin,
which complains about missing environment variables and recommends using
the command line tool to launch it.
Using AppleScript to create internal OS X alias to original application

This structure makes the alias application continue to open the target
application even if the target application is moved to a different path.

In order to accomplish this, AppleScript is used to create an OS X alias
to the original application, and the alias is bundled within the
application. The launcher script then runs the open command on the
internal alias, which then opens the target application.
Using shell script to launch application alias

Using pure AppleScript commands had unexpected behavior, including
launching application without initializing the, eg, launching a text
editor but not opening a blank document, as normally happens. Using
`open application` via `do shell script` in the launcher script appears
to resolve this issue.

For more information, also see: http://stackoverflow.com/a/22698574
Adding functionality for determining the alias app's target.
Refactoring to move launcher script into compile function

This script was being assigned as a constant while acting as a variable,
so moving into the #compile! method directly. This change also
simplified the signature of #compile! since it now only takes one
argument.