allow puppetlabs/inifile 4.x

This change adds "--keep-until-expiring" closer to letsencrypt binary because there can be a pipe or another
command at the end.

Here is an example of broken cron (a lot of parameters is omitted):

    certbot -d 'example.com' | grep "Congratulations" && (/sbin/service nginx reload) --keep-until-expiring

This change fixes it to:

    certbot --keep-until-expiring -d 'example.com' | grep "Congratulations" && (/sbin/service nginx reload)

add --keep-until-expiring closer to letsencrypt command in cron

FreeBSD 10 is EoL

This is now implemented in modulesync_config:
voxpupuli/modulesync_config#622

modulesync 2.10.0 / Drop FreeBSD 10 / Add FreeBSD 12

delete legacy travis directory

Fedora will never have EPEL. This makes it easier to keep supporting
Fedora.

Fedora 29 is EOL since November 26th. Since there's no actual code
change, it'll still continue to work for users.

I've noticed other PRs fail because puppet is trying to install the
dns_rfc2136 package before EPEL has been configured. The cleanest way of
fixing this seems to be to have the plugin class `require letsencrypt`.
There are only two resources in the `letsencrypt::plugin::dns_rfc2136`
and the `file` resource already required `Class['letsencrypt']`. Now the
`package` resource will too.

The base class already `contain`s `letsencrypt::install` and that
`include`s `epel` and configures the correct ordering.

Ensure EPEL is configured before installing plugin

#218 Switch to puppet-epel

allow to override --cert-name

Add Fedora 31, drop Fedora 29

modulesync 2.12.0

Use voxpupuli-acceptance

add manifest to install dns-route53 plugin, along with tests

See #227

fix typo in renew example

modulesync 3.0.0 & puppet-lint updates

release 6.0.0