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/command/org_test.go

@@ -1611,7 +1611,7 @@ func TestCommandSide_SetUpOrg(t *testing.T) {
 			name: "human added with initial mail",
 			fields: fields{
 				eventstore: expectEventstore(
-					expectFilter(), // add human exists check
+					expectFilter(), // add User (Human) exists check
 					expectFilter(),
 					expectFilter(
 						eventFromEventPusher(

internal/command/user_v2_model.go

@@ -409,7 +409,7 @@ func (wm *UserV2WriteModel) SetPasswordCodeSent(e *user.HumanPasswordCodeSentEve
 
 func (wm *UserV2WriteModel) Query() *eventstore.SearchQueryBuilder {
 	// remove events are always processed
-	// and username is based for machine and human
+	// and username is based for service account and user (human)
 	eventTypes := []eventstore.EventType{
 		user.UserRemovedType,
 		user.UserUserNameChangedType,