JBIDE-18094

I opted to make it 2 methods because I didn't like how it looked without setModuleRequiresFullPublish,  where the logic was inlined into launch(). 

As for why it's not one method in some other class, I've already stated, The logic was in the full-publish action, which is in as.ui. I needed it in as.wtp.core. I could have duplicated the code, but I thought that would be wasteful, and opted to make a new class who's purpose was to launch a full publish operation after setting the appropriate flags on all modules for a given server. 

It originally *was* one simple method... in a class in as.ui.  But it needed to be used in as.wtp.core, and, then, I thought it was made more clear by separating out the inner for-loop into its own method. 

I had considered making the methods static rather than have a constructor, but I felt that would be bad form, and didn't like it.