Sample template generation creates templates that set values

[eeverman]

Describe the bug
The andhow.properties file template that is generate creates unexpected values for Properties that don't have defaults. For instance, this is a sample output for a StrProp value that doesn't have a default:

org.yarnandtail.andhow.load.std.StdJndiLoader.CONFIG.ADDED_JNDI_ROOTS = [String]

If someone used this auto-generated template and didn't edit this line, the value would be set to [String]. This is not the intention.

To Reproduce
Either force template generation or fail a startup.

Expected behavior / Actual behavior
The template should be usable as generated without side-effects. Its OK to write in default values, since this will have no effect. However, if the property [Type] is written into values that have no default, the user may not notice that the template has values set and get unintended values.

The type is already listed - AndHow should just leave the entries empty, which would be interpreted as not set.
For JNDI sample entries, it probably just needs to comment out the xml that actually sets the value.

Implementation note: I've decided to not have any value writing in properties files, even if there is a default (just leave the value portion empty always).

Environment (please complete the following information):
All

[eeverman]

Fixed by #619