render icons of entrance=* with less priority than other icons

[Klumbumbus]

Buildings often have apartments in the upper floors and shops in the ground floor. So lately I tag addresses and shops this way: I give the building outline the adress data and place the shop as node as part of the outline with the tag entrance=yes. This way you can add multiple shops with multiple entrances to one building and the address data is not redundant. The address data can derived from the building outline. (Nominatim sadly doesn't do this at the moment.) For example: ​http://www.openstreetmap.org/way/108569788 is the building outline with the address data and it has two nodes: an amenity=pub ​http://www.openstreetmap.org/node/2767937065 and a shop=haidresser ​http://www.openstreetmap.org/node/2767937062. Both do also have the tag entrance=yes. If you open that area in JOSM you see that for the pub, the pub icon is rendered and for the hairdresser the entrance icon is rendered. Though, the hairdresser icon is much more important than the entrance icon. So if you tag a lot in this schema, you see just a lot of entrance icons instead of different shop, amenity,leisure (,...) icons.

During some tests I found out that it is sometimes very confusing, which icon JOSM renders. E.g. you can even create two identical nodes with entrance=yes and leisure=sports_centre; one rendering the sports_centre icon and the other the entrance icon. (I can give more information on this if needed.) I think the best would be always to prioritize all other icons over the entrance=* icons in rendering on nodes.

[Klumbumbus]

This seems to be fixed when new mapcss version of JOSM internal style ​http://josm.openstreetmap.de/browser/josm/trunk/styles/standard/elemstyles.mapcss goes live as default (instead of xml version). See #9691

[Klumbumbus]

This is fixed, because #9691 is done.