Handle standard streams redirection

[0x2c7]

There are some issues that mention Jard doesn't work well with foreman, pumactl, and similar apps redirect the standard stream. In addition, it doesn't work well with piping as well. This PR is to handle such cases by detecting real user's tty in case STDIN/STDOUT are not tty.

Some tested and covered in tests:

• Pipe stdin and stdout (covered in tests)
• Redirect stdin and stdout (covered in tests)
• Foreman (tested manually)

TODO in later PRs:

• What if Jard runs inside docker?
• What if Jard starts in an isolated process group, and doesn't have TTY at all?

Related issues:

• [BUG] breaks with foreman and rails #46
• Absolutely Gorgeous !! add documentation about stdin/stdout redirections precautions for hard #38

[nonnenmacher]

so good, works like charm.

I patched a line in the puma.rb file that is read by pumactl launcher if present.

around redirection just don't redirect stdout (by passing a nil)

stdout_redirect nil, './log/error.log', true

And it works perfectly.

As this is the recommended way for a Docker deployment, it should work (not tested yet).

But at least it allow a pretty decent experience, on a production machine as last ressort.
Thanks