[new release] ppxlib (0.32.0)

[NathanReb]

Standard infrastructure for ppx rewriters

• Project page: https://github.com/ocaml-ppx/ppxlib
• Documentation: https://ocaml-ppx.github.io/ppxlib/

CHANGES:

• Fix Longident.parse so it properly handles unparenthesized dotted operators
  such as +. or *.. (Add tests for parsing longident's with . ocaml-ppx/ppxlib#111, @rgrinberg, @NathanReb)

• raising an exception does no longer cancel the whole context free phase(Allowing multiple errors to be reported in one pass of the context_free phase ocaml-ppx/ppxlib#453, @Burnleydev1)

• Sort embedded errors that are appended to the AST by location so the compiler
  reports the one closer to the beginning of the file first. (Sort errors by location before appending them to the AST ocaml-ppx/ppxlib#463, @NathanReb)

• Update Attribute.get to ignore loc_ghost. (Fix hash used by Attribute.get ocaml-ppx/ppxlib#460, @ceastlund)

• Add API to manipulate attributes that are used as flags (cumbersome flag attributes ocaml-ppx/ppxlib#408, @dianaoigo)

• Update changelog to use ISO 8061 date format: YYYY-MM-DD. (Changed dates in changelog to ISO 8601 format: YYYY-MM-DD. ocaml-ppx/ppxlib#445, @ceastlund)

• Replace Caml with Stdlib. (Replace Caml with Stdlib ocaml-ppx/ppxlib#427, @ceastlund)

• When a transformation raises, the last valid AST is used as input to the upcoming
  transformations. All such errors are collected and appended as
  extension nodes to the final AST (Driver: Multiple errors can be reported. ocaml-ppx/ppxlib#447, @Burnleydev1)

• Fix a small mistake in the man pages: Embededding errors is done by default with
  -as-pp, not with -dump-ast (Fix misleading error in man page ocaml-ppx/ppxlib#464, @pitag-ha)

• Set appropriate binary mode when writing to stdout especially for Windows
  compatibility. (Binary mode when writing to stdout on Windows ocaml-ppx/ppxlib#466, @jonahbeckford)

[NathanReb]

I'm going through the revdeps failures but there's quite a fair amount and most of them seem to be unrelated.

So far the only thing relevant I found is that nuscr.2.0.0 is getting new deprecation alerts from this release but the test failure seems unrelated so no actual relevant breakage.

[NathanReb]

nuscr.2.0.0 is getting new deprecation alerts from this release

Actually, scratch that, the deprecation alerts come from base!

[NathanReb]

We did introduce a breaking change by mistake that triggered a build failure on ocsigen-i18n. I'll fix it and re-release.