[TM-307] No (&) in types

Description

Problem: using (&) type operator (used in types of instructions) is not too convenient, when it comes to error messages GHC tends to wrap these in paretheses. Compare:

Integer & (Natural & (MText & s))

against

Integer : Natural : MText : s

Solution: stop using (&) in basic Lorentz methods.

We do not remove or deprecate it because someone may find it neater despite the problems it causes. But making the base library cause hardly-readable error messages is not an option.

Related issue(s)

✅ Checklist for your Merge Request

Related changes (conditional)

• Tests (see short guidelines)

  • If I added new functionality, I added tests covering it.
  • If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

• Documentation

  • I checked whether I should update the docs and did so if necessary:
    • Root README and other README.md files
    • Haddock
    • docs/
  • I updated changelog files of all affected packages released to Hackage if my changes are externally visible.

Stylistic guide (mandatory)

• My commits comply with the following policy.
• My code complies with the style guide.