Also add docstrings.

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>

because @converse-headless wasn't available

which logs less on the INFO loglevel

Remove demo/without_bundled_dependencies.html

That way the tarball we upload to Github is the same as the one that we
get from installing Converse via NPM.

CC @ChaosKid42

To create the tarball containing the assets, just run `npm pack`.
This is the same tarball that gets uploaded to https://npmjs.org

when were generating only the CSS

Removed CSS rules which don't appear to be used anywhere.

This is a precursor to also testing (and implementing) that a chat pages
through MAM results (see #1549)

Remove unused method.

Also add a new API method `api.disco.features.get` for the use-case
where you still want the feature object to be returned.

- Use native `getTime` method instead of moment's `valueOf`
- Use toISOString() instead of moment().format()
  This makes the code timezone independent since we're now globally using UTC.

Messages (received directly or via MAM) are stored in a backbone
collection that's kept sorted by the message's "time" attribute.
Various parts of the codebase rely on this behavior.

For regular messages, the time attribute is generated by
`moment().format()`, which generates a timestamp in the browser's
local timezone, for example "...+02:00".

For MAM messages, we would previously copy the "delay.stamp" value
into the "time" attribute verbatim. However, that value is generated
by the server and is unlikely to be in the same timezone locale.

ISO timestamps expressed in different timezones cannot be sorted
lexicographically, breaking the premise of keeping the messages
collection sorted by time.

instead of accepting a callback functions.

Room auto-configuration broke if the config form contained fields with type `fixed`