Store modules in pride-local config

[lptr]

Instead of having a separate .pride/modules file, the list of current modules should be stored in .pride/config.

This would allow the developer to share this single file with others, who could re-create the same pride for themselves. (See #81)

Modules could be stored like this:

modules.0.name = boxfish-geometry
modules.0.url = https://github.com/prezi/boxfish-geometry
modules.0.vcs = git

[lptr]

Or it could look like this:

modules.boxfish-geometry.url = https://github.com/prezi/boxfish-geometry
modules.boxfish-geometry.vcs = git

[lptr]

However, with the latter there is no option to have, say, . in the module name, which might be overly limiting (think of typical Eclipse project names that include the package name in the project name).

[lptr]

Actually, that's not true: Commons Configurations will escape the key, so we can use the second format.

[lptr]

This should be done now.