Create a new ruby portlet option is disabled when there is a groovy portlet inside that same portlet application.

Steps to reproduce:
- Create a portlet app.
- Add a Groovy portlet.
- Now try to add a ruby portlet to the same portlet app. You can see the "Create Portlet" option in the portlet wizard
is not selected and all the text field for portlet details are also disabled. 

Expected behaviour : While creating the first ruby portlet in a portlet app, the "Create Portlet" option should be
selected by default and all text field should be enabled.

Fix :
Before showing the portlet wizard (for non java portlet), the system checks if there is already a portlet available of
that type. If yes, then the "Create portlet" option doesn't get selected by default, hence giving a chance to create a
normal ruby/groovy/php page without creating a new portlet for that page. This is handled by a framework and all non
java portlet's implementation has to implement an interface.