Change default chmod behaviour, update xinetd dependency.

[nosmo]

Until after v3.0.7, rsync's chmod directives completely ignored octal chmods, only paying attention to "Du+rwx"-style specifiers. When upgrading from rsync v3.0.7 to v3.0.10, I hit an issue wherein rsynced directories became inaccessible because the 644 permissions are applied to all files and directories, and directories lacked executable bits. Rather than change this chmod to a comprehensive "Du+rwx,go+rx,Fu+rwx,go+r", I think it makes sense to disable the chmod by default and allow users to configure their own chmods per-module and otherwise maintain the original modes set on files.

This PR also updates the fixtures to use the now-puppetlabs-maintained xinetd repository and updates test facts accordingly.

[esalberg]

I have a separate PR also dealing with chmod, but in a different manifest. We should make sure that they don't conflict (I think they should be okay?):
#83

[eputnam]

@nosmo , if you're still interested in getting this in, would you mind rebasing on master?

[nosmo]

Rebased!

[eputnam]

@nosmo I guess I'd rather see the defaults changed than dropping them altogether. Seems like these are defaults that a lot of people probably rely on.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Hugh Nowlan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}