Prohibit duality in application bindings

[maxonfjvipon]

In EO we don't support application with and without binding at the same time, so the next code is invalid:

man
  "Jeff":name # "Jeff" object is bound to the "name" attribute of "man"
  42          # "42" is bound to 2nd attribute of "man" but not explicitly

All application arguments must be either with @as attribute or without it:

The next XMIR is valid:

<o base="man">
  <o base="string"/>
  <o base="number"/>
</o>

The next XMIR is also valid:

<o base="man">
  <o base="string" as="name"/>
  <o base="number" as="age"/>
</o>

But the next XMIR is not valid:

<o base="man">
  <o base="string" as="name"/>
  <o base="number"/>
</o>

Let's add check that would catch such cases with severity critical

[yegor256]

@h1alexbel can you help?

[h1alexbel]

@yegor256 yes