Update MSIE version check.

- Target MSIE < 11.
Polish inspector attributes overflow.

- 21px line-height.
- Bold attribute names.
- Make indicator a little bit bigger.
- Also remove max-width of query in title bar.
Request direct url to skip redirect.

* Add trailing slashes data and management endpoints
so there's no redirect since that's where Safari
loses the Authorization header.
No collision on item properties with node-id and rel type.

- Change so database autoset node-id and relationship type
 are referenced as <id> and <type> while user set properties
still are referenced as {propName} for caption in style / grass.
Lift decision on which PlanType to use up to ExecutionPlan.run

This ensures that we use the same plan for both the profiled and normal case
Rename PlanType to ExecutionMode
Expose schemaStateFlush() from kernel
Test interaction of different execution modes with query caching
Existance of node/rel is checked before deletion
Removed outdated scripts and man pages
Add support for argumentIds in the exhaustive planner
Add support for hinted leaf plans in the exhaustive planner
Merge pull request #3679 from oskarhane/2.2-no-collision-item-properties-with-db

Fix collision on item properties and node-id / rel type in GraSS.
Merge pull request #3645 from oskarhane/2.2-inspector-overflow-polish

Polish inspector attributes overflow and indicator.
Merge pull request #3653 from oskarhane/2.2-msie-ribbon-less-than-11

Update MSIE version check.
Merge pull request #3668 from oskarhane/2.1-webadmin-call-correct-url

Request direct url to skip redirect in wedadmin.
Better output for compare expressions in plan descriptions.

When using unnamed identifiers instead of just removing all unnamed identifiers
leading to outputs like `NOT( == )`, we now output `NOT(anon[22] == anon[42])`.
Fixed issue with prematurely exhausted iterator.

By exhausting the iterator on initialization, some queries lead to a lot
of unnecessary dbhits, e.g.
````
profile MATCH (n:topic)-[r]->(m:topic) return n,r,m limit 1;

+------------------+------+----------+-------------+----------------------+
|         Operator | Rows |   DbHits | Identifiers |                Other |
+------------------+------+----------+-------------+----------------------+
|            Slice |    1 |        0 |             |         {  AUTOINT0} |
|           Filter |    1 |        1 |             | hasLabel(m:topic(0)) |
| TraversalMatcher |    1 | 11292978 |             |              m, r, m |
+------------------+------+----------+-------------+----------------------+

Total database accesses: 11292979
````
should ideally only touch a small portion of the graph but ends up touching something like
50% instead. This fix I believe fix this.
Fixes a race allowing transactions to be rotate away before applied

The problem was that there was a window after appending the transaction to
the log and before marking that transaction as committed where a log
rotation could come in and rotate the log. The rotator would not wait for
the transaction(s) that had just been appended, and potentially also
forced since it hadn't even been marked as committed yet.
So a crash right after or at least before the changes of such
transactions would have been applied and fully forced to the store would
be lost since the transaction describing those changes would not be
recovered.
Merge pull request #3699 from tinwelint/2.2-commit-vs-rotate-race-fix

Fixes a race allowing transactions to be rotate away before applied