Remove YAML service definition

Author: mnocon

docs/ai_actions/extend_ai_actions.md

@@ -121,7 +121,7 @@ See the code sample below, together with a matching service definition:
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 28, 33) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 28, 33, remove_indent=True) =]]
 ```
 
 The `ibexa.ai.action.handler` tag is used by the `ActionHandlerResolverInterface` to find all the Action Handlers in the system.
@@ -141,7 +141,7 @@ The example handler uses the `system_prompt` option, which becomes part of the A
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 34, 41) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 34, 41, remove_indent=True) =]]
 ```
 
 The created Form Type adds the `system_prompt` field to the Form.
@@ -158,7 +158,7 @@ You can create your own formatting by creating a class implementing the [Options
 The following service definition switches the options rendering to the other built-in options formatter, displaying the options as JSON.
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 64, 66) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 64, 66, remove_indent=True) =]]
 ```
 
 ## Custom Action Type use case
@@ -184,7 +184,7 @@ The class needs to define following  parameters of the Action Type:
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 42, 50) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 42, 50, remove_indent=True) =]]
 ```
 
 The service definition introduces a custom `app.connector_ai.action.handler.audio_to_text` service tag to mark all the handlers capable of working with this Action Type.
@@ -222,7 +222,7 @@ The following example adds a checkbox field that indicates to the Action Handler
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 51, 58) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 51, 58, remove_indent=True) =]]
 ```
 
 The built-in `Ibexa\Bundle\ConnectorAi\Form\FormMapper\ActionConfiguration\ActionTypeOptionsFormMapper` renders the Form Type in the back office when editing the Action Configuration for a specific Action Type (indicated by the `type` attribute of the `ibexa.connector_ai.action_configuration.form_mapper.action_type_options` service tag).
@@ -238,7 +238,7 @@ The Action Type options provided in the Action Context dictate whether the times
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 59, 63) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 59, 63, remove_indent=True) =]]
 ```
 
 ### Integrate with the REST API
@@ -256,7 +256,7 @@ Start by creating an Input Parser able to handle the `application/vnd.ibexa.api.
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 68, 72) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 68, 72, remove_indent=True) =]]
 ```
 
 The `TranscribeAudioAction` is a value object holding the parsed request data.
@@ -283,7 +283,7 @@ The resolver is activated when `application/vnd.ibexa.api.ai.AudioText` media ty
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 73, 76) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 73, 76, remove_indent=True) =]]
 ```
 
 - A visitor converting the response value object into a serialized REST response:
@@ -294,7 +294,7 @@ The resolver is activated when `application/vnd.ibexa.api.ai.AudioText` media ty
 ```
 
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/services.yaml', 77, 81) =]]
+[[= include_file('code_samples/ai_actions/config/services.yaml', 77, 81, remove_indent=True) =]]
 ```
 
 You can now execute a specific Action Configuration for the new custom Action Type through REST API by sending the following request:
@@ -331,8 +331,9 @@ This template embeds the AI component, but only if a dedicated `transcript` fiel
 ```
 
 And add it to the SiteAccess configuration for the `admin_group`:
+
 ``` yaml
-[[= include_file('code_samples/ai_actions/config/packages/ibexa_admin_ui.yaml') =]]
+[[= include_file('code_samples/ai_actions/config/packages/ibexa_admin_ui.yaml', remove_indent=True) =]]
 ```
 
 The configuration of the AI component takes the following parameters: