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/go.mdx

@@ -17,7 +17,7 @@ At the end of the guide you should have an API with a protected endpoint.
 ## Prerequisites
 
 This will handle the OAuth 2.0 introspection request including authentication using JWT with Private Key using our [Go SDK](https://github.com/zitadel/zitadel-go).
-All that is required, is to create your API, create a private key and a personal access token for a service user.
+All that is required, is to create your API, create a private key and a personal access token for a service account.
 
 ### Set up application and obtain keys
 
@@ -54,15 +54,15 @@ And make sure to download it, as you won't be able to retrieve it again.
 
 Now we need to create a *Personal Access Token* to authenticate the application requests.
 
-On the user view, switch to *Service Users* and create a new one.
+On the user view, switch to *Service Accounts* and create a new one.
 
 ![](../../../public/img/go/api-service_user_panel.png)
 
-Give the service user a name and a username. Select `Bearer` as *Access Token Type*.
+Give the service account a name and a username. Select `Bearer` as *Access Token Type*.
 
 ![](../../../public/img/go/api-create_service_user.png)
 
-### Create service user and personal access token (PAT)
+### Create service account and personal access token (PAT)
 
 Once done, from the left panel of the user management, click on Personal Access Token and create a new one.