Also allow <button> elements for entity browser dialog triggers

Problem/Motivation

The current implementation explicitly looks for the entity browser dialog trigger to be of type <input />. This makes the entity browser not usable e.g. when a theme relys on <button /> elements to be used for all buttons.

Proposed resolution

• Look for <button /> elements, too - use :input instead if input in jQuery selectors

Remaining tasks

• Provide a patch to fix the issue

User interface changes

API changes

Data model changes