docs: add api-requests guide

[Solant]

Background

Some guides on where to place API requests. I added only the English version first to gather feedback.

[Copilot]

Pull Request Overview

Adds a centralized guide on where and how to organize API request logic and removes inline examples from other docs in favor of linking to the new guide.

• Moved detailed “where to store request” examples out of the auth guide into a standalone API-requests guide
• Removed an outdated auto-generation types section in the types guide
• Introduced api-requests.md with shared and slice-specific patterns, client setup, and generator recommendations

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
i18n/en/docusaurus-plugin-content-docs/current/guides/examples/types.md	Removed “Auto-generation of types” section
i18n/en/docusaurus-plugin-content-docs/current/guides/examples/auth.md	Replaced inline API‐request examples with a reference link
i18n/en/docusaurus-plugin-content-docs/current/guides/examples/api-requests.md	Added new guide covering shared/slice-specific request patterns

Comments suppressed due to low confidence (2)

i18n/en/docusaurus-plugin-content-docs/current/guides/examples/types.md:431

• [nitpick] The removal of the auto-generation section removes guidance on handling generated types; consider linking to an external guide or summarizing key steps for regenerating types in a dedicated folder.

## Auto-generation of types

i18n/en/docusaurus-plugin-content-docs/current/guides/examples/api-requests.md:14

• [nitpick] Indent this list under 'A typical file structure would be:' by two spaces (e.g. - 📂 shared) to ensure proper nesting and consistent markdown rendering.

- 📂 shared

[illright]

I really like how the new page reads, great work! I have some concerns about how the other pages link to this one though — I'd like to see the link more naturally integrated into the narrative

[illright]

Great stuff, thanks!