feat: idp v2 api GetIDPByID (#8425)

# Which Problems Are Solved

GetIDPByID as endpoint in the API v2 so that it can be available for the
new login.

# How the Problems Are Solved

Create GetIDPByID endpoint with IDP v2 API, throught the GetProviderByID
implementation from admin and management API.

# Additional Changes

- Remove the OwnerType attribute from the response, as the information
is available through the resourceOwner.
- correct refs to messages in proto which are used for doc generation
- renaming of elements for API v3

# Additional Context

Closes #8337

---------

Co-authored-by: Livio Spring <livio.a@gmail.com>

docs/docusaurus.config.js

@@ -356,6 +356,14 @@ module.exports = {
                 categoryLinkSource: "auto",
             },
           },
+          idp_v2: {
+            specPath: ".artifacts/openapi/zitadel/idp/v2/idp_service.swagger.json",
+            outputDir: "docs/apis/resources/idp_service_v2",
+            sidebarOptions: {
+              groupPathsBy: "tag",
+              categoryLinkSource: "auto",
+            },
+          },
         },
       },
     ],

docs/sidebars.js

@@ -673,12 +673,24 @@ module.exports = {
               link: {
                 type: "generated-index",
                 title: "Feature Service API",
-                slug: "/apis/resources/feature_service/v2",
+                slug: "/apis/resources/feature_service_v2",
                 description:
                   'This API is intended to manage features for ZITADEL. Feature settings that are available on multiple "levels", such as instance and organization. The higher level instance acts as a default for the lower level. When a feature is set on multiple levels, the lower level takes precedence. Features can be experimental where ZITADEL will assume a sane default, such as disabled. When over time confidence in such a feature grows, ZITADEL can default to enabling the feature. As a final step we might choose to always enable a feature and remove the setting from this API, reserving the proto field number. Such removal is not considered a breaking change. Setting a removed field will effectively result in a no-op.\n'
               },
               items: require("./docs/apis/resources/feature_service_v2/sidebar.ts"),
             },
+            {
+              type: "category",
+              label: "Identity Provider Lifecycle",
+              link: {
+                type: "generated-index",
+                title: "Identity Provider Service API",
+                slug: "/apis/resources/idp_service_v2",
+                description:
+                  'This API is intended to manage identity providers (IdPs) for ZITADEL.\n'
+              },
+              items: require("./docs/apis/resources/idp_service_v2/sidebar.ts"),
+            },
           ],
         },
         {