Motivation: The UI parts of YaST modules are little tested. The few cases that
do test the dialog code need to mock away all UI calls. So Ancor came up with
an idea to mock the user interaction but let libyui run the dialog construction
(so that it can check for us whether we are not passing nil somewhere).

This does not work because libyui / yast2-ycp-ui-bindings rely on y2base to
select the desired frontend (Qt/ncurses) and report an error about needing to
call SetServerOptions.

Finding the correct initialization code in yast2-core and adding it to
yast2-ruby-bindings should not be hard.