[#236] Handle constructor annotation in Lorentz

Description

Problem: Good smart contracts should have annotations for nearly each meaningful component of their parameter and storage types. So we should enforce usage of annotations and somehow indicate if a contract does not have annotations that we think it should have. However, we should do it carefully for parameter, so that we don't introduce extra entrypoints.

Solution: Allow generating constructor annotation for other meaningful parts of parameter and storage while ensure no extra entrypoints are introduced.

Related issue(s)

Resolves #236 (closed)

✅ 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.