* add Nim 2.0.2 to supported versions

* updated nimble release name

* one more

Although NEP1 suggests not having spaces around these infix operators,
this creates an exception to the normal infix spacing rules.

In spite of this recommendation, lots of code out there maintains spaces
around the operators which makes decision based on "existing practice"
hard.

Adding to the complexity is in order to not break the AST, the code must
take care to remove the spaces only in cases where the infix is not
followed by another operator - this means that we _sometimes_ will put
spaces around these infixes and sometimes not, again leading to
irregularity.

Since there's no consensus in existing code, the rule is irregular and
causes implementation complexity, this PR removes the exception and
formats `..` and `..<` with spaces.

When multiple dot-separated calls don't fit on a single line, use a long
format similar to lists to put each on a new line.

The section "short form" was restored to its 0.2 format to allow the
before-`=` part of the section to stay on the same line as the section
keyword.

This reduces the overall indent of the (long) RHS which gives it better
chances to be formatted nicely.

Treating `.` as complex leads to complex formatting where it is not
desired, such as module-prefixing and trivial field accesses - this
plays well with omitting `()` in trivial calls as well.

* ensure long if-expressions are line-broken correctly
* render first condition of `of` on the same line
* document what is simple

There should be at least two calls for stacking mode to kick in

Use proc-renderer for lambdas also (fixes parameter format as well)

* stricter CI

* fix formatting

Update README.md to include NeoVim integration using neoformat plugin. 

+ sbdchd/neoformat#491

When rendering the right-hand expression of a keyword like `return` or
an assignment, sometimes we would add a newline and indent.

This PR avoids such extra indent/newlines by allowing partial
expressions such as function calls to continue on the same line like so:

```nim
let myvariable = functioncall(
  arg0, arg1, ...
)
```

This saves significant amounts of space as we avoid the extra indent
that previously would apply to the arguments in this case.

Includes several random doc comment fixes for free!

If the second argument of an infix doesn't fit on the current line but
fits on a new line, prefer a newline before the argument over partially
formatting it on the same line as the operator.

This gives a preference to having the operator alone on the end of the
line and nicely lines up parenthesized expressions in general.