Stop bundling the JMS transport in axis2.war

No default axis2.xml enables a JMS listener or sender, yet every WAR carried the
transport and its JNDI lookup code. It was not usable as shipped in any case:
jakarta.jms-api is an API with no provider, so a WAR wanting JMS always had to
add a broker client. The module is unchanged and still ships in the binary
distribution's lib/, so a standalone server is unaffected; the distribution
builds its WAR from that directory, which is why the exclude belongs there too.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>