fix: proposal to solve "FamixUMLRoassalBackend does not show all relevant associations when displaying CoastersCollector example"

[bart-at-qqdatafruits]

fix: proposal to solve "FamixUMLRoassalBackend does not show all relevant associations when displaying CoastersCollector example" as illustrated in moosetechnology/Famix#1070

[NicolasAnquetil]

@tinchodias Hello Martin, do you have the rights to approve this PR ?

[bart-at-qqdatafruits]

@tinchodias Hello Martin, do you have the rights to approve this PR ?

I assume the Roassal team needs to review also if the proposal PR is in line with the intended / preferred semantics involved or the proposal needs review in that perspective

[tinchodias]

@tinchodias Hello Martin, do you have the rights to approve this PR ?

yes I can! I will check

[tinchodias]

Is this change backwards compatible? in a fast read I just did, it looks like you extracted code to a hook. I imagine this way you can override in your subclasses with custom shapes?

[bart-at-qqdatafruits]

Hi @tinchodias,

I will review the error and review the integration of the proposal made.

Please reject the PR.

Thanks in advance,

[bart-at-qqdatafruits]

added additional commit that should do away with all errors (see commit message)
note that maybe more importantly is the question if the intent of Roassal-UML is intended to implement an UML Class Diagram, allowing to add associations.

[bart-at-qqdatafruits]

I apologize for not having reviewed the testcases and examples before the previous commit.
I will have a look at example08HierarchyPacker as it still fails on Pharo13 build 723.
Normally tests on Pharo13 and Pharo14 should have failed too.
I will review the log of the Pharo12 tests to see how I can improve further testing from my side

[tinchodias]

Thanks @bart-at-qqdatafruits!

For some reason, I had to click on a "Run workflow" button, else the CI doesn't run automatically.

Maybe this is your first contribution to the project, and after the first merge, the CI will run automatically.

The error in Pharo 12 is unrelated (see #141)