nfs4: fix incrementing owner sequence id in some cases

If in a compound request an error occurs before the operation that takes
sequence id is executed (e.g. OPEN or LOCK) do not increment sequence id
regardless of the error code.

nfs4: use exponential backoff when the server ask to wait

nfs4: Prevent OpenState::_ReclaimLocks from being called recursively

When server reboots again when share reservations or locks are being
reclaimed there is a risk that HandleErrors will invoke Reclaim(( again
making it crash due to some double locks and more importantly making
these two attempts to reclaim resources conflict and cause some much harder
to recover from server errors.

Instead all that, when server is rebooted again while recovering from previous
reboot the recovery is aborted, the client retries its original request and
then proper recovery occurs completly on a new server instance.

nfs4: Do not increment open owner sequence number when reusing lock owner

nfs4: Multiple style fixes

nfs4: Fix handling of retried CLOSE requests

nfs4: Add numerous assertion checks

nfs4, dns_resolver: fix numerous style violations

nfs4: Make the client more configurable

nfs4: Add basic emulation of named attributes

nfs4: Make sure that request are properly sequenced

nfs4: Fix server reboot recovery

nfs4: Reclaim delegations after server reboot

nfs4: Use global open owner, check whether delegation was granted

nfs4: NFS4Object::HandleErrors needs OpenState or OpenFileCookie object

nfs4: Do not open too much files on server

nfs4: fix incrementing owner sequence id in some cases

If in a compound request an error occurs before the operation that takes
sequence id is executed (e.g. OPEN or LOCK) do not increment sequence id
regardless of the error code.

nfs4: use exponential backoff when the server ask to wait

nfs4: Prevent OpenState::_ReclaimLocks from being called recursively

When server reboots again when share reservations or locks are being
reclaimed there is a risk that HandleErrors will invoke Reclaim(( again
making it crash due to some double locks and more importantly making
these two attempts to reclaim resources conflict and cause some much harder
to recover from server errors.

Instead all that, when server is rebooted again while recovering from previous
reboot the recovery is aborted, the client retries its original request and
then proper recovery occurs completly on a new server instance.

nfs4: Do not increment open owner sequence number when reusing lock owner

nfs4: Multiple style fixes

nfs4: Fix handling of retried CLOSE requests

nfs4: Add numerous assertion checks

nfs4, dns_resolver: fix numerous style violations

nfs4: Make the client more configurable

nfs4: Add basic emulation of named attributes

nfs4: Make sure that request are properly sequenced

nfs4: Fix server reboot recovery

nfs4: Reclaim delegations after server reboot

nfs4: Use global open owner, check whether delegation was granted

nfs4: NFS4Object::HandleErrors needs OpenState or OpenFileCookie object

nfs4: Do not open too much files on server