Puppet Support

This would be really useful, and not just for librarian-puppet support. New tools or new versions of existing tools might require the modules api to function, and supporting it would go a long way towards making sure that Pulp can support all tools that make use of the forge api.

As discussed with bmbouter on IRC, here are more details about how to reproduce a testing environment for librarian-puppet:

• Have an already-working pulp_puppet repository setup, published either through http or https, and containing the `puppetlabs-apache` module.
• Install librarian-puppet
• Create a `Puppetfile` file, containing:

#!/usr/bin/env ruby
#^syntax detection

forge "https://.:pulp_repo_id@pulp_hostname/"

mod 'puppetlabs-apache', "1.4.1"

(make sure to edit the 'forge' URI)

• Run `librarian-puppet install --no-use-v1-api --verbose` in the same directory as the Puppetfile
• Observe it being unable to find any module.

For the record, I am using ruby1.9.3p484, puppet 3.4.3 as well as librarian-puppet v2.2.1.

This could be handy during development: https://forgeapi.puppet.com/#interactive-demonstration

This change is also needed by Puppet's r10k code management tool and Puppet Enterprise's Code Manager tool. Both tools require the /modules endpoint in addition to the /releases endpoint to deploy Puppet Modules from a Pulp repository.

Additionally, librarian-puppet was migrated from rodjek to Vox Pupuli some time ago as well. Project URL - https://github.com/voxpupuli/librarian-puppet.