feat: Automated regeneration of ServiceNetworking client (googleapis#12900)

Auto-created at 2025-01-31 13:12:17 +0000 using the toys pull request generator.

Author: yoshi-code-bot

clients/service_networking/lib/google_api/service_networking/v1/metadata.ex

@@ -20,7 +20,7 @@ defmodule GoogleApi.ServiceNetworking.V1 do
   API client metadata for GoogleApi.ServiceNetworking.V1.
   """
 
-  @discovery_revision "20250107"
+  @discovery_revision "20250129"
 
   def discovery_revision(), do: @discovery_revision
 end

clients/service_networking/lib/google_api/service_networking/v1/model/page.ex

@@ -21,7 +21,7 @@ defmodule GoogleApi.ServiceNetworking.V1.Model.Page do
 
   ## Attributes
 
-  *   `content` (*type:* `String.t`, *default:* `nil`) - The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+  *   `content` (*type:* `String.t`, *default:* `nil`) - The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
   *   `name` (*type:* `String.t`, *default:* `nil`) - The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
   *   `subpages` (*type:* `list(GoogleApi.ServiceNetworking.V1.Model.Page.t)`, *default:* `nil`) - Subpages of this page. The order of subpages specified here will be honored in the generated docset.
   """