build: detect new erlang version format correctly

- OTP 17.0 uses a different numbering system for releases and patches, but not semver.org
- the major version number will be bumped for the first time in 4 years
docs: update supported Erlang/OTP and SpiderMonkey versions

- matches what the code can support after last Mochiweb update
- update .travis.yml file to match 17.0 release
- update docs
Merge branch 'refs/heads/2200-feature-support-erlang-17.0'

- closes COUCHDB-2200

* refs/heads/2200-feature-support-erlang-17.0:
  docs: update supported Erlang/OTP and SpiderMonkey versions
  build: detect new erlang version format correctly
Fix comparison warning on ./configure
Use <%- when interpolating XSS targets

  - I tried to not be super heavy handed, only using <%- for values that
    could be set with XSS payloads or otherwise come from a user/data.
Fix setting autoconf flags for using nifs
Fix ejson nif configure against R14B04
COUCHDB-2233 - Correct HTML interpolation instances in documents.

Further updating instances of <%= and to <%- within documents to correctly handle HTML interpolation.

Tested for regression in
- 34.0.1847.131
- Safari 7.0.2

Signed-off-by: Alexander Shorin <kxepal@apache.org>
Apply workaround fix for replication checkpoints test against R14B01

R14B01 and R14B02 both are affected to OTP-9167 Erlang issue which
causes 4 tests failure because supervisor restarts worker with old
ChildSpec ignoring changes in use_checkpoint options.

This fix makes all tests passed, but leaves a notice in verbose mode
that there is a problem and how it could be resolved.

Another possible solution is to isolate test_use_checkpoints calls, but
this will be only hide the issue while it still may happened in prod.
Move Erlang 17 support to 1.6.0 release
Fauxton: do not underline help icons on hover

Addtionally, use <%- where no <%= is needed
Remove doubled event.preventDefault call
Fauxton: Configurable escaping of notifications

Sometimes we are passing static html-links to the notification-
helper. With the new setting `escape: false` the escaping for
the notifications can be disabled.

The default value is that all values are escaped, as long as
no value with `false` is passed for the option escape.
`undefined` and other falsy values will not unescape.

I updated all occurences where we are passing html to the
notifications, and added a comment, that people are careful, when
the passed message changes to e.g. a dynamic content generated
from users.
Fauxton: fix sorting for tasks on click

there is no node property, but a target, source or database
depending on the task
Fauxton: Extract a common filter component from logs

Create a reusable component from the filter that is used in logs,
that can be used in for tasks like
COUCHDB-2158 ("Apply filter with custom params on changes feed page")
and other situtations where a filter is needed.