splunk running as non-root user

new splunk installations can run as a non-root user if desired (this cookbook does not support switching between root and non-root, should it?)

There is a really ugly ruby_block which I tried pushing to a definition, spent 2+ days trying to get it to work, and then giving up.  We may even be able to skip this recursive chown if we can determine which of the Execute resources is spraying root owned files into $SPLUNK_HOME.

There are no tests for this change.  Should there be?
why are these modes all different? perhaps it would be cleaner to just make them all `00755` and iterate over a list?