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

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!

Start by reviewing the affected rules in ooasp_check.lp and ooasp_arity.lp, then compare their counterparts in asp_interactive_configuration/DOC.md. Trace how same-named attributes and associations from different classes produce no_instance_for_attribute, wrongtypeinassoc, and ooasp_arity results. Done means the Interactive Configuration API supports these cases consistently across the implementation and documented snippets.