feat(generator): support output_dir and build_extensions config for generated files

Now the code generator supports specifying a custom output directory and extension/name template for generated DI files via build.yaml ( and ). This allows placing all generated code in custom folders and using flexible naming schemes.

docs: update all user docs and tutorials to explain new output_dir/build_extensions config

- Added detailed usage and YAML examples to cherrypick_generator/README.md
- Synced full_tutorial_en.md and full_tutorial_ru.md (advanced codegen section) with explanation of new configuration and impact on imports
- Updated quick_start_en.md and quick_start_ru.md to mention advanced customization and point to tutorials
- Added troubleshooting and tips for custom output/imports in docs

doc/quick_start_en.md

@@ -19,7 +19,29 @@ There are two main methods for initializing a custom instance `toInstance ()` an
 
 Example:
 
-```dart
+```
+
+---
+
+## Advanced: Customizing Code Generation Output
+
+You can configure where generated files will be placed by updating your `build.yaml` (supports `output_dir` and `build_extensions`):
+
+```yaml
+targets:
+  $default:
+    builders:
+      cherrypick_generator|inject_generator:
+        options:
+          output_dir: lib/generated
+      cherrypick_generator|module_generator:
+        options:
+          output_dir: lib/generated
+```
+
+For full control and more examples, see the "Full Tutorial" or documentation on `build_extensions`.
+
+---
  // initializing a text string instance through a method toInstance()
  Binding<String>().toInstance("hello world");