JBIDE-18372 - tweaking progress monitors

So I tested it a lot with and without these parts. Theoretically, I should have similar lines for publishStart and publishFinish.  WTP is allocating sub monitors for these methods, and never marks them as done. It's my job to start, and then done() them. 

The problem is if I have the monitors in publishStart and publishFinish and publishServer,  then the actual publish (zip plus transfer) is really only like 40% of the monitor (depending on the number of modules being published, but for 1 module being published, it's 40%).  Basically, their weights are kinda... weird. 

So I decided to keep the start() and done() in only publishServer, not publishStart / publishFinish (for THIS publish method).  It makes it so the progress monitor advances to about 15%,  and when the publish is basically complete, the monitor is at around 78%.  

If I were to put it into all three of them, then the progress monitor would read like 40% before I even did anything, and around 80% afterwards. 

At this point it's kind of a value judgement and what I feel works best for the user... to see some progress in the beginning, then the slow increase during zip and mgmt calls, and then a fast end. 

Tested with an example project with 5000 files in it.