Emit an error if the user is trying to deploy a WAR via the invoker servlet in jboss 5.x

* src/platform/jboss/deployers/ejbinvokerservlet.py
  src/platform/jboss/deployers/jmxinvokerservlet.py
  -- It's possible that no fingerprints are valid for deploying; dont crash
  if we dont find any
  -- Added a check to ensure we're deploying a JSP payload when the JBoss
  fingerprint is version 5.x.  Only JSP's can be deployed, as we're invoking
  the DFS deployer.
Fix for issue #10

* src/platform/jboss/deployers/ejbinvokerservlet.py
  src/platform/jboss/deployers/jmxinvokerservlet.py
  -- If we could not detect the remote host, we should prompt for
  the user to either input a known version or guess.  It's not clear
  why this would happen, but as shown, it can.
  -- Added some comments
Fix attempt #2 for EJB/JMX servlets with invalid fps
For deployers sake, don't worry about HTTP header versions too much
Moved web shells into a resources folder as we begin to build up
our arsenal of deployable utilities/shells

* src/lib/resources
  -- This will now hold our web shells and generic resources.  Currently
  we have simplistic web shells, but I'd like to get a fuze.cfml equivalent
  written for JSP's to be used on tomcat/jboss.
  -- Added cmd.cfml, which is a very simple coldfusion web shell which
  can be used in coldfusion or railo
* src/platform/jboss/deployers/ejbinvokerservlet.py
  src/platform/jboss/deployers/jmxinvokerservlet.py
  -- Cleaned up the input prompt
Updated DFS deployer with new path of cmd.jsp
Fixed payload generator