[TM-317] Refactor scope-related constraints

Description

This is a preparation for introducing a new constraint for contract type.

In short, here I group constraints according to the scope they relate to - parameter, storage, constant, e.t.c, and make project code use this groups.

Related issue(s)

https://issues.serokell.io/issue/TM-317

✅ 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:
    • README
    • Haddock
    • docs/

Stylistic guide (mandatory)

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