Hardcoded interactions interfere with existing interactions in map

[StefanBrand]

A workaround on application side helps to mitigate the issue:

      // NOTE: workaround for drawtools capturing tooltip
      this.getEoxMap().selectInteractions["selectHover"].setActive(false);
      this.getEoxMap().selectInteractions["selectClick"].setActive(false);

Originally posted by @StefanBrand in #592 (comment)

As demonstrated in #592, the drawn feature captures the tooltip and does not give it back by itself. It has to be persuaded by setting its interactions' active state to false (see above).

Two general issues:

• There is no way to create drawtools without interactions: In the agri use case I do not want interaction with the drawn feature. The drawn feature serves as a way to select features on a different layer and I want that layer to stay interactive, including its tooltip.
• The hardcoded IDs are not unique enough: The hardcoded IDs ("selectHover" and "selectClick") are not ideal because they could easily conflict with the id of a manually configured interaction of the map.

Deliverable

• integration test with map, existing layers, drawtools and tooltip