CommunicationParameterRef: add a _build_odxlinks() method

[andlaus]

this allows to get rid of some special treatment of comparams in the diaglayer. (i.e., all objects featured by DiagLayer which have a ._resolve_references() should now also have .build_odxlinks())

Andreas Lauser <andreas.lauser@mercedes-benz.com>, on behalf of MBition GmbH.
Provider Information

[andlaus]

thanks for merging. I was quite a bit confused by the fact that you used a "rebase merge" since I thought I accidentally pushed this directly to main. For this reason, I think it would be good to use the "create merge commit" or "squash and merge" strategies for future PRs. (Come think of it, you might have used the latter one, but since there was nothing to squash, it probably just pushed unmodified patch of the PR...)

Did I miss a drawback of using merge commits (besides the messier history)?

[kayoub5]

I just used the merge button default settings.

the choice of merge strategy depends on how messy the pr history is
messy pr history : discard it by squashing
clean pr history: merge commit or rebase

[andlaus]

I just used the merge button default settings.

weird. maybe it remembers what you used the last time. Anyway, not a big deal; I was quite confused, but to a large extend this was because I did not expect this...

the choice of merge strategy depends on how messy the pr history is
messy pr history : discard it by squashing
clean pr history: merge commit or rebase

+1. that is my sentiment as well. I suppose it comes down to a github usability issue then...