Flex Gateway flex-external-processor OOM caused by WSDL Validation Policy retry loop with URL-encoded filenames

The flex-external-processor component receives policy update events via gRPC in a continuous loop. When the WSDLValidation policy
  attempts to load a WSDL file whose filename contains URL-encoded characters (e.g., %20 representing a trailing space), the Java schema
  loader fails to resolve the file path. The error logged is:

  Unable to load resource file:///tmp/unzip.../filename.wsdl null

  Because the failure is treated as transient, the policy is retried repeatedly on each configuration delivery cycle. Each retry extracts
  the WSDL zip bundle to a new /tmp/unzip* directory without cleaning up the previous extraction. This results in:

  - Progressive accumulation of /tmp/unzip* directories
  - Unbounded memory growth from temp files and schema parser objects not being released
  - Eventually OOM-kill of the flex-external-processor pod

  Versions affected: 1.13.1, 1.13.2, 1.13.3

  The issue does NOT affect WSDL files with clean filenames (no spaces or URL-encoded characters). Inbound flow (Inbound messages from
  citizens) works correctly. Only outbound messages that trigger the WSDL validation are affected.