fix: simplify deletion logic

[thomassedlmayer]

This PR removes the redundant getDeletedSceneEntites function and the corresponding calls.

The current logic seems a bit confusing to me. It compares the actually created lane/lane boundary scene entities with the previous...Ids lists which track the existence of IDs in the actual OSI messages (even if they are turned off for visualization). Also, the IDs in the state already have been updated to the current state and don't reflect the previous state anymore which makes it even more confusing. The logic actually leads to the deletion of physical/logical lane networks when the config parameters change but also a lot of deletions even if nothing has to be deleted (e.g. when config and lane/lane boundary ID presence hasn't changed):

I tried to fix and simplify it by checking the showLogicalLanes/showPhysicalLanes config parameters when getDeletedEntities is called and passing an empty list if the parameter is false, which also leads to deletion of the corresponding lane network if it was previously present.

@myemural Could you check out the changes?