Support multiple attributes/associations of the same name in Interactive Configuration API

[rtaupe]

In the Interactive Configuration API, there are several reasons why multiple attributes or associations of the same name but in different classes are not supported.

A (not necessarily exhaustive) list of these reasons:

• The cv no_instance_for_attribute in ooasp_check.lp may be wrongly produced if attributes of the same name appear in two different classes.
• There is a similar issue with the cv wrongtypeinassoc.
• The calculation of association arities (predicate ooasp_arity in ooasp_arity.lp includes only the association name, but not the names of the involved class names, in the heads of rules.

Attention: Many of these ASP snippets also occur in asp_interactive_configuration/DOC.md!

[gschennersie]

In OOASP it is assumed (but not checked) that the "name" of an attribute/association is actual an unique id within the knowledge base i.e. "frame_position" instead just "position". This way attribute/association/names are unambigous. Otherwise we would have to add an additional class parameter to every attribute and 2 class parameters to every association. Also association names denote the whole association/relation e.g. "frame_modules" and not the role of an association (as typically used in an object oriented setting). Roles are not modelled in OOASP.