chore(docs): User (Human) naming consistency (#11512)

# Which Problems Are Solved

Naming inconsistencies - User (Human)

# How the Problems Are Solved

Most of the occurrences have not been changed. `User (Human)` was mostly
changed when talking about code objects and where I felt it was
necessary to distinguish them from machine users.

When both human and machine user occurrences were found, the machine
user has been changed to service account (see
https://github.com/zitadel/zitadel/issues/11285)

# Additional Context

- Closes #11284

---------

Co-authored-by: Wim Van Laer <[email protected]>

internal/api/scim/integration_test/testdata/service_provider_config_expected.json

@@ -33,7 +33,7 @@
       "name": "Zitadel authentication token",
       "description": "Authentication scheme using the OAuth Bearer Token Standard",
       "specUri": "https://www.rfc-editor.org/info/rfc6750",
-      "documentationUri": "https://zitadel.com/docs/guides/integrate/service-users/authenticate-service-users",
+      "documentationUri": "https://zitadel.com/docs/guides/integrate/service-accounts/authenticate-service-accounts",
       "type": "oauthbearertoken",
       "primary": false
     }

internal/api/scim/resources/user_query_builder.go

@@ -69,7 +69,7 @@ func (h *UsersHandler) buildListQuery(ctx context.Context, request *ListRequest)
 		SearchRequest: searchRequest,
 	}
 
-	// the zitadel scim implementation only supports humans for now
+	// the zitadel scim implementation only supports User (Humans) for now
 	userTypeQuery, err := query.NewUserTypeSearchQuery(domain.UserTypeHuman)
 	if err != nil {
 		return nil, err