Split EntityId into LocalEntityId and ForeinEntityId

[JeroenDeDauw]

Most of the code [should distinguish / distinguishes] those and cannot work with both.

This was a proposal by Aleksey.

---

Is it true that most code can only work with one type? If so, that does sound like the addition of the foreign concept to EntityId is problematic. I'm not up to speed with the foreign stuff at all so can't judge this.

Thoughts @addshore @mariushoch @manicki @JonasKress ?

[JeroenDeDauw]

Theimo wrote:

I'm not saying the current
architecture does not have problems (it certainly has), but I know for
a fact that the current architecture was intentionally designed so
that all code that was previously able to consume (local) entity IDs
is able to consume prefixed ("foreign") entity IDs. It might be worth
evaluating this. If it turns out that most code can not deal with
both types of IDs, it might indeed be worth redoing this part of the
DataModel.