Explicitly set the umask for daemon in Debian init script

As discovered by danielbeck in #jenkins, daemon(1) does not inherit the parent
process's umask. The --umask flag is the means to set it explicitly.

Here I assumed $UMASK will always be set in `/etc/default/jenkins` since it is there in the stock version and it seems to be the norm elsewhere.

If this PR is accepted, one could make the argument that the calls to "umask" are no longer needed further down in the init script. I'll leave that up to someone else since I'm not sure if there was another intent for it.
Tested and nothing came to a screeching halt at least. I can't see how the init script could have created any files so I have no idea how that could have been affecting anything. I left the verbose message where it was since moving it changes the functionality drastically.