Fixes #1699

execising that

EPOLLPRI causes the waiter to report activity on a socket when there
is OOB data available. Since HTTP does not make use of OOB the data is
never read and the socket thus is always ready for read according to
the waiter. This causes the waiter to continously assign the session
to a worker only for the worker to find out there is no data sending
it back to the waiter. This continues until the request timeout_idle
has elapsed.

This problem does no constitute a DOS attack vector as the linger
timeout in the session SES_RxReq is still invoked, and this one does
not trigger on PRI. So the worker sleeps on that poll for
timeout_linger before sending the session back to the waiter, and
eventually is dropped on timeout_idle.

Fixes: #1674

This option controls the timeout for the initial VSM open operation

This makes query expression errors be reported before any VSM
connection related errors.

This sets the input cursor to be used by the query.

This is to avoid having to delete the VSLQ context during VSM reopen.

Also allows parsing of the query without having to open the VSM first,
to facilitate early error messages.

After VSLQ_Flush() there should not be any ready vtx' to get rid of.

It isn't internal

proxie'd addresses.

a workspace to 2^N doesn't result in 2^N+a allocations.

Report "sz_wanted" and "sz_actual" in VSC.

Clarify which addresses are in ReqStart and SessOpen

independent SES_RxReq() function.

Eliminate timeout_req and rely on timeout_idle to do the job.
(Length of this timeout still under debate on -dev)