Eclipse as a Java debugger for Zero applications

It seems that most of the options for debugging a Zero application involve modifying the zero.* script and/or setting up a runtime configuration in Eclipse. Since web IDE users will not be able to modify the zero.* script (unless they go to the command line, which seems to defeat the point), it seems like the simplest thing to do would be to import the application into an Eclipse workspace and use the existing debug facilities. Eclipse allows you to import a project without doing a copy, so we wouldn't have to worry about synchronization of changes during debug/test. There also wouldn't be any modification of files that came from a zero.* package, which is not supported activity under our EULA.

Assuming the CLI create task still generates .classpath and .project files, we can hide these in the web IDE view but still have them present for when users want to import to Eclipse and debug w/o additional configuration.