docs(Storage): Improve Getting Started and Overview

[DevTKSS]

GitHub Issue (If applicable): closes #2630

PR Type

What kind of change does this PR introduce?

• Documentation content changes

What is the current behavior?

• Missing complete Getting Started Page for Storage Extensions, the existing one is very few and by that incomplete, not usable "as is"

What is the new behavior?

• Improved Overview Page with more details about when to use Storage Extensions like file types
• Mentioned additional Libraries for not directly serialization supporting storage files
• Added a includes usable md file for future Storage How-To's to the Getting Started Guide.
• Added a full Storage Getting Started Guide with Mvvm & Mvux specific VM setup code diff and specifics that will enable to set up the future storage files properties correctly "CopyToOutputDirectory"

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs => Sample App used provided from Steeve Bilogan in Discussion on unoplatform/main repository #19088 for the correct usage in Hostbuilder etc.
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Contains NO breaking changes
• Associated with an issue (GitHub or internal)

Other information

Thank's again to @kazo0 for support to get the setup correct!

The PR #2710 will be simplifyed to "just" add the mentioned samples in exchange to the not existing API Reference one sample usage per function. More detailed Guides after this should then be added to the Chefs Reciept book, but I would at this point not know that it is reading from assets => future appdata nested files similar to my MvuxGallery is doing.

Internal Issue (If applicable):

[unodevops]

⚠️⚠️ The build 169006 has failed on uno.extensions.

[unodevops]

⚠️⚠️ The build 169030 has failed on uno.extensions.

[DevTKSS]

@kazo0 @Kunal22shah so from what I see in the src, up from we having a non blank Preset app, we would always have the Hosting inlcuded. But on the other hand, as this is already pulling in the .UseStorage() at the very end, it could be optional, to add the Storage Feature, but in my opinion, we should tell to do this either way like on all other Features.

[Copilot]

Pull Request Overview

This PR improves the Storage extension documentation by adding a comprehensive Getting Started guide and enhancing the existing overview. The changes provide developers with clear step-by-step instructions for setting up and using the Storage extension in their Uno Platform applications.

Key changes:

• Added a complete Getting Started guide with setup instructions for both MVUX and MVVM patterns
• Enhanced the Overview page with more details about file types and when to use Storage extensions
• Created reusable documentation includes for prerequisites

Reviewed Changes

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

Show a summary per file

File	Description
doc/Learn/includes/getting-help.md	Added reference to Uno.Sdk documentation
doc/Learn/Storage/toc.yml	Added Getting Started guide to navigation
doc/Learn/Storage/includes/use-storage-prerequisites.md	Created reusable prerequisites include
doc/Learn/Storage/StorageOverview.md	Enhanced overview with file type guidance and better structure
doc/Learn/Storage/Storage-GettingStarted.md	Added comprehensive Getting Started guide
doc/ExtensionsOverview.md	Added Storage extension to main extensions list
build/ci/cspell.json	Added spell check entries for XML doc tags
build/ci/.markdownlint.json	Disabled emphasis-as-heading rule

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[DevTKSS]

Fun fact, while the docs are tellin us, we require Hosting for DI, our app is fine at runtime without it 🤷 and yes, the app I used to test this with is using the DI Container for Keyed Services