Allow deployment of local portlet applications without a jetspeed- name prefix

Jetspeed currently only supports local (portal context) deployment of portlet applications when their name is prefixed with "jetspeed-".

To allow local deployment of any portlet application, I'll extend the DeployPortletAppEventListener to also treat portlet application wars put in a specific local application staging dir as local portlet applications.
By default configuration, Jetspeed will now also treat any portlet application war put in WEB-INF/deploy/local as local portlet application.

Note: A local portlet application is only useful for providing portlets which don't need full web container functionality like servlets or resource lookups as those are not supported.