move the properties stored in "paths.properties" into SVN properties stored on the .savana file

the data currently recorded in "paths.properties" (paths to trunk, branches, user branches) is really something that is a function of each project, not a global truth. If a user uses savana on multiple projects, each one could be configured differently. additionally, it is wrong to have this configured on each client in any case - by changing these values on my own machine, I can violate the principals set up by the project owner as to where things go.

the right solution seems to be to just attach these values onto the .savana file as SVN properties. When someone runs the "savana createmetadatafile" to bootstrap the project, there will be three optional arguments to configure the trunk, branches, and user branches to use. these will default to "trunk", "branches", and "branches/user".

The open issue is whether we need to copy these values verbatim to the .savana file in any branches, or whether we can easily get to the one from the trunk to look up these values. copying them seems to be the easiest, and it prevents having to walk a trail of branches back to the root for deeply nested workspaces.