Upgrade librarian-puppet to version 1.3.2

Upgrade librarian-puppet using:

```sh
bundle update librarian-puppet
```

Now that [we're using Puppet 3.6][puppet-3.6], we should be using
version 3 of the Puppet Forge API[1][2].

Upgrade libarian-puppet, which as of version 1.1.0[3] can support the
new API[4].

The change to actually start using the newer API is in the next commit.

[1]: https://tickets.puppetlabs.com/browse/PUP-2093
[2]: https://docs.puppetlabs.com/puppet/3.6/reference/release_notes.html#module-tool-changes
[3]: https://github.com/rodjek/librarian-puppet/blob/a028cc5189d788762f68fd961a569a4b4fc16a61/Changelog.md#110
[4]: https://github.com/rodjek/librarian-puppet/commit/f7b59976e25055e14603d4db5624416a99d289b4

[puppet-3.6]: https://github.com/gds-operations/puppet-skeleton/commit/abf2511ecc610cb9818eada01908e432947e6ca4)
Upgrade to Puppet Forge API version 3

Change the URL in `Puppetfile` and `Puppetfile.lock` so that we're using
v3 of the Puppet Forge API.

This also has the benefit of providing transport layer security (HTTPS)
for the API connection, which gives us some guarantee that we are
connecting to the correct server.

The line `LIBRARIAN_PUPPET_USE_V1_API: '1'` was added when I ran
`bundle exec librarian-puppet install`. I can set it to false by running:

```sh
bundle exec librarian-puppet install --no-use-v1-api
```

`--use-v1-api` is the default[1][2] but libarian-puppet ignores this
setting for the official Puppet Forge[3] and uses the v3 API. So leave
it as-is to make running `librarian-puppet install` simpler.

[1]: https://github.com/rodjek/librarian-puppet/tree/2f0423e883b374ff805500acf1ab9986f2690e1d#how-to-use
[2]: https://github.com/rodjek/librarian-puppet/blob/2f0423e883b374ff805500acf1ab9986f2690e1d/lib/librarian/puppet/cli.rb#L64
[3]: https://github.com/rodjek/librarian-puppet/blob/2f0423e883b374ff805500acf1ab9986f2690e1d/lib/librarian/puppet/source/forge.rb#L154
Merge pull request #14 from gds-operations/use-v3-api

Upgrade to Puppet Forge API version 3