Bidirectional reflexive association causes problems

[Matthias Schoettle]

Steps to reproduce:

• Create a design model with one class
• Create a reflexive association
• Make it bidirectional
• Change one of the ends to 1..*
• Save

The save will fail, because there are mappings that point to operations that were deleted upon changing the multiplicity.

Another problem occurs when changing back from bidirectional to unidirectional. Then, an out of bounds exception occurs when trying to delete one of the operations.

[Matthias Schoettle]

References #491: Adds return type into determining whether two operations are the same.

→ <<cset 2bc3fa0d8ac8>>

[Matthias Schoettle]

Resolves #491: Ensures that mapped operations are deleted if there are not mapped elsewhere.

Also ensures that the operations of the opposite side are deleted for bidirectional associations (where Associated might have operations).

→ <<cset 57998fe4ff2e>>

[Matthias Schoettle]

References #491: Fixes bug introduced in commit 2bc3fa0 where an operation would not be unique if another operation with the same name but different parameters exists.

→ <<cset 4bd20e1c1bca>>