fix: use a single translator for middleware (#10633)

# Which Problems Are Solved

Comparing the v3 and v4 deployments we noticed an increase in memory
usage. A first analysis revealed that it might be related to the
(multiple) initialization of the `i18n.Translator`, partially related

# How the Problems Are Solved

Initialize the tranlator once (apart from the translator interceptor,
which uses context / request specific information) and pass it to all
necessary middleware.

# Additional Changes

Removed unnecessary error return parameter from the translator
initialization.

# Additional Context

- noticed internally
- backport to v4.x

(cherry picked from commit a0c3ccecf7)

internal/api/scim/serrors/errors_test.go

@@ -7,6 +7,7 @@ import (
 	"testing"
 
 	"github.com/stretchr/testify/assert"
+	"golang.org/x/text/language"
 
 	"github.com/zitadel/zitadel/internal/i18n"
 	"github.com/zitadel/zitadel/internal/zerrors"
@@ -97,9 +98,10 @@ func TestErrorHandler(t *testing.T) {
 		t.Run(tt.name, func(t *testing.T) {
 			req := httptest.NewRequest("GET", "/", nil)
 			recorder := httptest.NewRecorder()
-			ErrorHandler(func(http.ResponseWriter, *http.Request) error {
-				return tt.err
-			}).ServeHTTP(recorder, req)
+			ErrorHandler(i18n.NewZitadelTranslator(language.English))(
+				func(http.ResponseWriter, *http.Request) error {
+					return tt.err
+				}).ServeHTTP(recorder, req)
 			assert.Equal(t, tt.wantStatus, recorder.Code)
 
 			if tt.wantBody != "" {