Removed default values from xinetd.conf and added params for each (and tests!)

I believe that this puppet module providing un-changeable defaults in the xinetd.conf makes too many assumptions about the users environment. Maybe they have a version of xinetd that doesn't support some of the settings provided? Maybe they want to have specific default settings that they don't have to duplicate for each individual service?

Taking these variables __out__ of the xinted.conf and adding them as parameters gives us maximum flexibility for users, and allows the __native__ xinetd to use its own system defaults. 

I know this is a different behavior than what it currently does, but I believe it is better than having the hard-coded default values as they are now, which I believed are copied from debian? However, admins can get the same behavior as before by providing the params, or simply not specify them to get the built-in xinetd defaults.