[jmesnil]

Replace the static ssl/ directory (which contained expired certificates
last generated in January 2023 with weak 1024-bit client keys) with a
new ssl-gen Maven module that generates fresh PKCS12 keystores and
truststores on every build using keytool-maven-plugin.

All consumers (testsuite, examples service and client modules) now copy
the required files directly from ssl-gen/target/generated-ssl/ at build
time instead of referencing hard-coded static files.

Key changes:

• Add ssl-gen/ module: generates server.keystore.p12, server.truststore.p12,
  client.keystore.p12, client.truststore.p12, client.truststore.pem plus
  CLI scripts using keytool-maven-plugin (2048-bit RSA, 365-day validity)
• Remove all static SSL binary files (expired certs, weak keys)
• Move configure-elytron-*.cli scripts to ssl-gen/src/main/resources/
  and update them to use PKCS12 format
• Testsuite: copy server keystores to WildFly config dir at
  process-test-resources; fix test code to use relative-to=jboss.server.config.dir
  instead of fragile relative path hacks; update two-way TLS code to
  load PKCS12 via KeyManagerFactory instead of PEM private key streams
• Examples service: replace maven-antrun copy with maven-resources-plugin;
  update CLI script paths to reference ssl-gen output
• Examples client: copy SSL files from ssl-gen output to target/classes;
  update two-way TLS code for PKCS12 KeyManagerFactory

[jmesnil]

@darranl Do you mind reviewing the ssl-gen module? I used your doc at https://github.com/user-attachments/files/32770020/TEST-CERTIFICATE-KEYSTORE-GENERATION.md to drive the changes and modernize a bit the generation (using PKCS12 instead of JKS).

I still had to import and use BouncyCastle to export the private keys that were needed by grpcurl (which afaict is a Go tool that does not support PKCS12).

@hpehl To verify the examples, I also simplified their use and did parts of #490 (at least the service parts to leverage WildFly provisioning).

[darranl]

Writing the PEM files is something we could plan for the future so makes sense to use BC for now, we have reading support so adding writing support makes sense.

[jmesnil]

@hpehl I think this is ready for review. Before it is merged, I'll squash all the commits if that's ok with you?

[hpehl]

LGTM! Thanks @jmesnil