Fix Meilisearch doc issues

[Alirexaa]

Closes #

This pull request includes minor changes to the CommunityToolkit.Aspire.Meilisearch project, focusing on documentation and configuration updates.

Documentation updates:

• src/CommunityToolkit.Aspire.Meilisearch/AspireMeilisearchExtensions.cs: Updated the summary comment to correctly refer to MeilisearchClient instead of Meilisearch.

Configuration updates:

• src/CommunityToolkit.Aspire.Meilisearch/README.md: Added a comma after the Endpoint value in the JSON configuration example.

PR Checklist

• [ ] Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• [ ] Based off latest main branch of toolkit
• [ ] PR doesn't include merge commits (always rebase on top of our main, if needed)
• [ ] New integration
  • [ ] Docs are written
  • [ ] Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• [ ] Tests for the changes have been added (for bug fixes / features) (if applicable)
• [ ] Contains NO breaking changes
• [ ] Every new API (including internal ones) has full XML docs
• [ ] Code follows all style conventions

Other information

[Alirexaa]

@aaronpowell, We should add some rules in .editorconfig to ensure our XML docs are always valid. I saw this issue in previous PRs too.