KeyCloak integration tests failing on some OSX Dev machines

### Describe the bug

When attempting to verify the 1.10 release I ran into an issue trying to run the KeycloakFileIT suite.

```
./gradlew :polaris-runtime-service:intTest --tests "RestCatalogKeycloakFileIT.testDropTableWithPurge"
```

For example would give a cryptic error about the quarkusTestPort being not set correctly. No other errors or warnings were surfaced.

Walking through with a debugger, the containers were starting correctly but the attempt to create roles in the Keycloack container was failing with a 403.

```
HttpResponseProxy{HTTP/1.1 403 Forbidden [Cache-Control: no-store, Pragma: no-cache, content-length: 64, Content-Type: application/json, Referrer-Policy: no-referrer, Strict-Transport-Security: max-age=31536000; includeSubDomains, X-Content-Type-Options: nosniff, X-Frame-Options: SAMEORIGIN] ResponseEntityProxy{[Content-Type: application/json,Content-Length: 64,Chunked: false]}}
```

The Docker instance on my OSX seemed to have started correctly and in debug mode, I attempted to hit the URI being used by the test suite and got the following site back

Which I don't think should be happening since we are in dev mode ... but seems to anyway.

Any other usages of the AdminClient are also failing with 403's

### To Reproduce

_No response_

### Actual Behavior

_No response_

### Expected Behavior

_No response_

### Additional context

_No response_

### System information

_No response_

Start by running ./gradlew :polaris-runtime-service:intTest --tests "RestCatalogKeycloakFileIT.testDropTableWithPurge" and inspect the KeycloakFileIT suite, the Keycloak container, and AdminClient role-creation path. Compare the failing OSX behavior with the expected dev-mode endpoint; done means the integration test runs successfully and AdminClient operations no longer return 403.

Written by the indexing model from the issue text.