chore: Service Account Naming Consistency (#11557)

# Which Problems Are Solved

Inconsistent naming of service account, found in the following
variations:

  - Machine User
  - machine user
  - Service User
  - Machine Account
  - Technical Account
  - User: Type Machine

# How the Problems Are Solved

Attentive search and replace.

Localizations have been translated using Copilot

# Additional Changes

Some unused methods have been removed from the Go code.

# Additional Context

- Closes #11285

apps/docs/content/examples/secure-api/python-django.mdx

@@ -4,8 +4,8 @@ sidebar_label: Django
 ---
 
 import AppJWT from '../imports/_app_jwt.mdx';
-import ServiceuserJWT from '../imports/_serviceuser_jwt.mdx';
-import ServiceuserRole from '../imports/_serviceuser_role.mdx';
+import ServiceAccountJWT from '../imports/_serviceaccount_jwt.mdx';
+import ServiceAccountRole from '../imports/_serviceaccount_role.mdx';
 import SetupPython from '../imports/_setup_python.mdx';
 
 This integration guide demonstrates the recommended way to incorporate ZITADEL into your Django Python application.
@@ -25,13 +25,13 @@ Before we can start building our application, we have to do a few configuration
 
 <AppJWT components={props.components} />
 
-### Create Serviceuser
+### Create Service Account
 
-<ServiceuserJWT components={props.components} />
+<ServiceAccountJWT components={props.components} />
 
-### Give Serviceuser an authorization
+### Give Service Account an authorization
 
-<ServiceuserRole components={props.components} />
+<ServiceAccountRole components={props.components} />
 
 ### Prerequisites
 
@@ -42,8 +42,8 @@ At the end you should have the following for the API:
 - `.json`-key-file for the API, from the application
 - ID of the project
 
-And the following from the Serviceuser:
-- `.json`-key-file from the serviceuser
+And the following from the Service Account:
+- `.json`-key-file from the service account
 
 ## Setup new Django application