JBIDE-18287 and JBIDE-14001 - persistence of single deployables does not...

... match callers current use of API.

Callers currently all using absolute paths from workspace when requesting modules or paths. This has been unified to use absolute paths when creating and loading the persisted list. 
This addition is a fun little piece of trivia:  
  If you made 1 project (ProjectA) and made 1 file deployable (FileA.xml),  then ProjectA/.settings/etc would show a deployable list of "FileA.xml". 

If you then made a 2nd project, ProjectB, and a 2nd xml file, FileB.xml, and made it deployable,  ProjectB/.settings/blahblah would show 2 entries:  FileB.xml\nFileA.xml

Clearly this is yet another bug, and doesn't belong there, since FileA.xml should only be stored in the .settings of ProjectA, not in ProjectB. 

So... I just thought I'd fix that here while I was at it ;)