client: exclude jdk15on BouncyCastle artifacts from the shaded jar

The client shade config only excluded the jdk18on BouncyCastle artifacts,
which are shipped as separate jars in the management server lib folder.
If a stale or transitive dependency pulls in bcprov/bcpkix/bctls-jdk15on,
the old classes are bundled into the fat jar and can shadow
bcprov-jdk18on depending on the classpath order of lib/*, failing with
NoSuchFieldError (e.g. xmss_SHAKE128_512ph) when the root CA module starts.

Author: weizhouapache

client/pom.xml

@@ -979,6 +979,10 @@
                                     <exclude>org.bouncycastle:bcprov-jdk18on</exclude>
                                     <exclude>org.bouncycastle:bcpkix-jdk18on</exclude>
                                     <exclude>org.bouncycastle:bctls-jdk18on</exclude>
+                                    <exclude>org.bouncycastle:bcprov-jdk15on</exclude>
+                                    <exclude>org.bouncycastle:bcpkix-jdk15on</exclude>
+                                    <exclude>org.bouncycastle:bctls-jdk15on</exclude>
+                                    <exclude>org.bouncycastle:bcutil-jdk15on</exclude>
                                     <exclude>com.mysql:mysql-connector-j</exclude>
                                     <exclude>org.apache.cloudstack:cloud-plugin-storage-volume-storpool</exclude>
                                     <exclude>org.apache.cloudstack:cloud-plugin-storage-volume-linstor</exclude>