Also fix a bug in the code dermining whether an XMLElement stanza is only a chat state notification

* _.isNil
* _.noop
* _.isNull

We do that in `clearSession` and otherwise when we auto-reconnect we end
up without a roster.

to `show_chat_state_notifications`

Fixes #1548

Shadow dom: TypeError: Cannot read property 'parentElement' of null caused by MinimizedChatsToggleView

If we've fetched the roster before within this session, then we don't
have to do so again, regardless of whether versioning is supported or
not, otherwise, even if we have a cached roster, we still need to get
the latest one again.

Otherwise `converse.features` cache id contains `null` instead of the
user JID and it doesn't clear correctly.

by not logging in automatically when `auto_login` is `false` and we're
using anonymous, external or prebind authentication.

For `authentication` set to `login` the situation is much more
ambiguous, since we don't have a clear distinction between wether we're
restoring a previous session (`keepalive`) or whether we're
automatically setting up a new session (`auto_login`).

So currently if *either* `keepalive` or `auto_login` is `true` and
`authentication` is set to `login`, then Converse will try to log the
user in.

Instead we should only query for newly created chats.

`sendIQ` now takes a flag to turn of rejection of the promise and to
resolve on error IQs instead.

even if the `_converse.bosh_session` instance does not exist.

We do this to avoid trying to reconnect with stale tokens upon
reconnection. Especially relevant for anonymous connections, but could
also be applicable when switching between websocket and BOSH connections
when reconnecting.

Also renamed `startNewBOSHSession` to `startNewPreboundBOSHSession`

I.e. also when we're reconnecting.

Otherwise the `_converse.bosh_session` object doesn't get recreated and
we don't cache the BOSH tokens.

above logging in with passed in JID and password, since the password
might be an expired token.

otherwise values get tacked on, causing problems when reconnecting.

Because when we reconnect anonymously, we get a new JID, so it's as if
it's a completely new user.

So that the BOSH connection will be restored before we trigger `connectionInitialized`

It's unlikely that `keepalive` needs to be set to `false`, but there are
some edge cases where it might be useful.

Here's a breakdown of the different configurations of `keepalive` and `auto_join`:

---

* auto_login: false, keepalive: true

This is the default config. Users need to log in manually, but then
Converse will try to reconnect them when the page reloads.

* auto_login: true, keepalive: true

Also very popular configuration. Used with `credentials_url` or `prebind_url`.

* auto_login = `true`, keepalive = `false`

Not sure what this could be useful for. No currently known application.

* auto_login = `false`, keepalive = `false`

Useful when you want some kind of specific action to trigger login, but
you don't want to maintain that state across page reloads.

Also relevant when using a websocket connection with anonymous login.
With websocket it's impossible to maintain anonymous sessions across page
reload because the the session gets removed server-side as soon as the
websocket connection drops and the server won't accept a full JID with
password for an anonymous connection anyway (which could happen upon
page reload when Converse tries to login in again if `keepalive` was `true`).