Refactor murano-dashboard tests

Now some murano-dashboard tests (such as 'create_delete_tomcat', 'create_delete_telnet' etc.) are dependent from changes in ui forms of corresponding packages in app-incubator and can be broken. Need to avoid such situation and do not rewrite tests after these changes.
Solution:
- leave uploading and usage of minimum number of apps from app-incubator just for checking main catalog features
- remove tests which create / remove specific apps
- create specific ui form that contain fields of different types and validation, that has ability to create related applications
- write tests using special test app (test on creation/deletion, validation tests etc)