Add --nowait/--timeout to logs

[0xmichalis]

tbh I don't see any value in --nowait or why someone would use it but anyway since it is supported by build-logs and all of the machinery is in place, we should probably add it.

[smarterclayton]

NoWait exists because clients may very well not want to wait for logs to be available - if something hasn't started, the effective log output is nothing.

[0xmichalis]

How about making the default timeout configurable instead? --timeout=0 would equal to --nowait, plus I can now specify how much I want to wait (more or less than the default 10s we currently have for builds and deployments).

[smarterclayton]

Making it configurable isn't unreasonable, but waiting on the server side is generally bad and is only for naive clients. It has to be upper bounded with something for admin control.

[openshift-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close