Description
Describe the bug
When using no-conflict for the press event, a ui5-press event is dispatched as expected, but the press event is also dispatched.
Expected behavior
If I provide a no-conflict for an event, the assumption is that there is other framework or future browser functionality that provides some functionality with the original event name (example: hammer js fires a press). If the app has a press handler for the hammerjs usage, getting an event from the ui5 webcomponent is wrong.
additional difficulties
The original event names are used in the templates, and the event names are decided at build time. This means all components using events of other components they embed should also use the no-conflict event name as the orignal one will stop being fired.