Removed references to detached code

[XAML-Knight]

Fixes #4440

Need to remove references to detached code, as they appear in the Community Toolkit Sample App as empty placeholders.

PR Type

What kind of change does this PR introduce?

• Bugfix

What is the current behavior?

Detached code appears in the Sample App, as blank sample pages

What is the new behavior?

Detached code no longer appears in list of available pages, in the Sample App

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] Tested code with current supported SDKs
• [ ] New component
  • [ ] Pull Request has been submitted to the documentation repository instructions. Link:
  • [ ] Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
  • [ ] If control, added to Visual Studio Design project
• [x] Sample in sample app has been added / updated (for bug fixes / features)
  • [ ] Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• [ ] New major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
• [ ] Tests for the changes have been added (for bug fixes / features) (if applicable)
• [ ] Header has been added to all new source files (run build/UpdateHeaders.bat)
• [x] Contains NO breaking changes

Other information

Unable to locate documentation that would suggest the empty sample pages could potentially contain hyperlinks to the new locations (on Github or NuGet) of the detached code.

[ghost]

Thanks XAML-Knight for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[Nirmal4G]

Docs still point to the correct location and can't we update the project links to the new location instead of completely removing those sections?

[michael-hawker]

Yeah, these are currently here intentionally to provide discoverability to these more non-UI parts of the Toolkit:

If you don't have the docs repo checked-out locally during development though, they will indeed not show anything, but none of the docs appear if you're not doing that.

It's ok for us to have doc-only pages in the current sample app.

[michael-hawker]

@Sergio0694 we should figure out a plan for how we want to handle at least the MVVM Sample app and getting that in the store, eh? @nmetulev maybe we need a toolkit publisher based account or something that we can use to centralize app submissions from?