[Bug]: HTTP Post transform in pipeline receives http 302 from servlet exposed on the same(or another) apache hop instance

### Apache Hop version?

2.8.0

### Java version?

22.0.1 2024-04-16

### Operating system

Windows

### What happened?

HTTP Post transform calling another apache hop servlet results in HTTP 302 status code. Calling the same servlet from another client like soapUI, results in HTTP 200.

Create 2 pipelines for exposing 2 webservices. Issue happens in the same apache hop server instance and also in different instances, like 2 docker images

From 1 pipeline try to call the second one and wait for a response, print out the HTTP code.

endpoint from second pipeline
https://hop-snd-server.cloud.com/hop/webService?service=MockWS",

From log:

2024/05/24 10:13:13 - Hop - Pipeline opened.
2024/05/24 10:13:13 - Hop - Launching pipeline [testRedirectMock]...
2024/05/24 10:13:13 - Hop - Started the pipeline execution.
2024/05/24 10:13:13 - testRedirectMock - Executing this pipeline using the Local Pipeline Engine with run configuration 'local'
2024/05/24 10:13:13 - testRedirectMock - Execution started for pipeline [testRedirectMock]
2024/05/24 10:13:13 - Generate random value.0 - Finished processing (I=0, O=0, R=1, W=1, U=0, E=0)
2024/05/24 10:13:13 - Set field value to a constant.0 - Finished processing (I=0, O=0, R=1, W=1, U=0, E=0)
2024/05/24 10:13:14 - Write to log.0 -
2024/05/24 10:13:14 - Write to log.0 - ------------> Linenr 1------------------------------
2024/05/24 10:13:14 - Write to log.0 - testReq =
2024/05/24 10:13:14 - Write to log.0 - result =
2024/05/24 10:13:14 - Write to log.0 - httpRestulCode = 302
2024/05/24 10:13:14 - Write to log.0 -
2024/05/24 10:13:14 - Write to log.0 - ====================
2024/05/24 10:13:14 - HTTP post.0 - Finished processing (I=0, O=0, R=1, W=1, U=0, E=0)
2024/05/24 10:13:14 - Write to log.0 - Finished processing (I=0, O=0, R=1, W=1, U=0, E=0)
2024/05/24 10:13:14 - HTTP client.0 - Finished processing (I=0, O=0, R=0, W=1, U=0, E=0)
2024/05/24 10:13:14 - testRedirectMock - Pipeline duration : 0.431 seconds [ 0.431" ]
2024/05/24 10:13:14 - testRedirectMock - Execution finished on a local pipeline engine with run configuration 'local'

### Issue Priority

Priority: 2

### Issue Component

Component: Hop Server, Component: Pipelines, Component: Transforms

Start with the HTTP Post transform and Hop Server servlet behavior described in the report. Reproduce the case with two pipelines, either on one server or separate Docker instances, and compare the returned status with the soapUI request. Done means the reported pipeline-to-servlet call no longer unexpectedly returns HTTP 302, with the behavior covered by an appropriate test.

Written by the indexing model from the issue text.