Expose lcb_cntl(..., LCB_CNTL_SKIP_CONFIGURATION_ERRORS_ON_CONNECT, ..)

There is a special mode which helps users to manage stale bootstrap node list.

Use case:

1) setup and deploy application to bootstrap with node1,node2,node3
2) over the time, admins eject node1 and it might still be listening on 8091
3) the application should skip LCB_AUTH_ERROR errors and LCB_BUCKET_ENOENT on node1 and continue with node2

Obviously after successful bootstrap, the list of "known" nodes will be updated for the particular connection. The problem in on-disk configuration