fix(api): naming cleanup in user and session service (#6379)

* fix(api): rename first and last name to given and family name, intent to idp_intent, remove _ actions

* fix merge

* fully rename intent to idp intent in api

---------

Co-authored-by: Tim Möhlmann <tim+github@zitadel.com>

docs/docs/guides/integrate/login-ui/_select-account.mdx

@@ -9,7 +9,7 @@ The list of session IDs can be sent in the “search sessions” request to get
 
 ```bash
 curl --request POST \
-  --url https://$ZITADEL_DOMAIN/v2alpha/sessions/_search \
+  --url https://$ZITADEL_DOMAIN/v2alpha/sessions/search \
   --header 'Accept: application/json' \
   --header 'Authorization: Bearer '"$TOKEN"''\
   --header 'Content-Type: application/json' \
@@ -77,4 +77,4 @@ curl --request POST \
 		}
 	]
 }
-```
+```

docs/docs/guides/integrate/login-ui/external-login.mdx

@@ -20,17 +20,18 @@ Send the following two URLs in the request body:
 2. ErrorURL: Page that should be shown when an error happens during the authentication
 
 In the response, you will get an authentication URL of the provider you like.
-[Start Identity Provider Flow Documentation](/docs/apis/resources/user_service/user-service-start-identity-provider-flow)
+[Start Identity Provider Intent Documentation](/docs/apis/resources/user_service/user-service-start-identity-provider-intent)
 
 ### Request
 
 ```bash
 curl --request POST \
-  --url https://$ZITADEL_DOMAIN/v2alpha/users/idps/$IDP_ID/start \
+  --url https://$ZITADEL_DOMAIN/v2alpha/idp_intents/start \
   --header 'Accept: application/json' \
   --header 'Authorization: Bearer '"$TOKEN"''\
   --header 'Content-Type: application/json' \
   --data '{
+  "idp_id": "$IDP_ID",
   "successUrl": "https://custom.com/login/idp/success",
   "failureUrl": "https://custom.com/login/idp/fail"
 }'
@@ -62,15 +63,15 @@ After the user has successfully authenticated, a redirect to the ZITADEL backend
 
 ## Get Provider Information
 
-ZITADEL will take the information of the provider. After this, a redirect will be made to either the success page in case of a successful login or to the error page in case of a failure will be performed. In the parameters, you will provide the intentID, a token, and optionally, if a user could be found, a user ID.
+ZITADEL will take the information of the provider. After this, a redirect will be made to either the success page in case of a successful login or to the error page in case of a failure will be performed. In the parameters, you will provide the IDP intentID, a token, and optionally, if a user could be found, a user ID.
 
 To get the information of the provider, make a request to ZITADEL.
-[Get Identity Provider Information Documentation](/docs/apis/resources/user_service/user-service-retrieve-identity-provider-information)
+[Retrieve Identity Provider Intent Documentation](/docs/apis/resources/user_service/user-service-retrieve-identity-provider-intent)
 
 ### Request
 ```bash
 curl --request POST \
-  --url https://$ZITADEL_DOMAIN/v2alpha/users/intents/$INTENT_ID/information \
+  --url https://$ZITADEL_DOMAIN/v2alpha/idp_intents/$INTENT_ID \
   --header 'Accept: application/json' \
   --header 'Authorization: Bearer '"$TOKEN"''\
   --header 'Content-Type: application/json' \
@@ -120,7 +121,7 @@ After successfully authenticating using your identity provider, you have three p
 ### Login
 
 If you did get a user ID in the parameters when calling your success page, you know that a user is already linked with the used identity provider and you are ready to perform the login.
-Create a new session and include the intent ID and the token in the checks.
+Create a new session and include the IDP intent ID and the token in the checks.
 This check requires that the previous step ended on the successful page and didn't’t result in an error.
 
 #### Request
@@ -136,9 +137,9 @@ curl --request POST \
 	"user": {
       		"userId": "218662596918640897"
     	},
-	"intent": {
-      		"intentId": "219647325729980673",
-      		"token": "k86ihn-VLMMUGKy1q1b5i_foECspKYqei1l4mS8LT7Xzjw"
+	"idpIntent": {
+      		"idpIntentId": "219647325729980673",
+      		"idpIntentToken": "k86ihn-VLMMUGKy1q1b5i_foECspKYqei1l4mS8LT7Xzjw"
     	}
   }
 }'
@@ -164,8 +165,8 @@ curl --request POST \
   --data '{
   "username": "minni-mouse@mouse.com",
   "profile": {
-    "firstName": "Minnie",
-    "lastName": "Mouse",
+    "givenName": "Minnie",
+    "familyName": "Mouse",
     "nickName": "Mini",
     "displayName": "Minnie Mouse",
     "preferredLanguage": "en",
@@ -206,4 +207,4 @@ curl --request POST \
     "displayName": "Minnie Mouse"
   }
 }'
-```
+```

docs/docs/guides/integrate/login-ui/mfa.mdx

@@ -69,7 +69,7 @@ Request Example:
 
 ```bash
 curl --request POST \
-  --url https://$ZITADEL_DOMAIN/v2alpha/users/$USER_ID/totp/_verify \
+  --url https://$ZITADEL_DOMAIN/v2alpha/users/$USER_ID/totp/verify \
   --header 'Accept: application/json' \
   --header 'Authorization: Bearer '"$TOKEN"''
   --header 'Content-Type: application/json' \
@@ -188,4 +188,4 @@ curl --request POST \
 }'
 ```
 
-You have successfully registered a new U2F to the user.
+You have successfully registered a new U2F to the user.

docs/docs/guides/integrate/login-ui/username-password.mdx

@@ -24,8 +24,8 @@ curl --request POST \
   "userId": "d654e6ba-70a3-48ef-a95d-37c8d8a7901a",
   "username": "minnie-mouse",
   "profile": {
-    "firstName": "Minnie",
-    "lastName": "Mouse",
+    "givenName": "Minnie",
+    "familyName": "Mouse",
     "nickName": "Mini",
     "displayName": "Minnie Mouse",
     "preferredLanguage": "en",