fix(core): document flag to allow keycloak container to run on M4 machines (#1993)

### Proposed Changes

*

### Checklist

- [ ] I have added or updated unit tests
- [ ] I have added or updated integration tests (if appropriate)
- [ ] I have added or updated documentation

### Testing Instructions

---------

Co-authored-by: Sean Trantalis <[email protected]>

Author: jakedoublev

docker-compose.yaml

@@ -7,7 +7,6 @@ services:
     - ./keys/localhost.crt:/etc/x509/tls/localhost.crt
     - ./keys/localhost.key:/etc/x509/tls/localhost.key
     - ./keys/ca.jks:/truststore/truststore.jks
-    # This is kc 24.0.1 with opentdf protocol mapper on board
     image: keycloak/keycloak:25.0
     restart: always
     command:
@@ -43,6 +42,7 @@ services:
       KC_HTTPS_CERTIFICATE_FILE: "/etc/x509/tls/localhost.crt"
       KC_HTTPS_CERTIFICATE_KEY_FILE: "/etc/x509/tls/localhost.key"
       KC_HTTPS_CLIENT_AUTH: "request"
+      # JAVA_OPTS_APPEND: "-XX:UseSVE=0" # Uncommenting resolves SIGILL with Code 134 when running on a machine with an M4 chip: https://github.com/keycloak/keycloak/issues/36008
     ports:
       - "9001:9001"
       - "8888:8888"