ClientLauncher relies on full metadata to obtain classpath

There is a circularity problem with how the app client launcher obtains the client classpath by downloading the JBossClientMetaData from the server. This can include deployment specific interfaces that require the client classpath to load. The classpath information needs to be made available separately from the JBossClientMetaData and a class loader created before loading the JBossClientMetaData.