docs: format query suggestion tutorial with proper steps

[Ashlesha-MSFT]

Category

• Content fix

Related issues

• fixes SPFx Docs Update for content : query-suggestion-tutorial-building.md #10681

What's in this Pull Request?

• Proper numbered lists, nested bullets, and fenced code blocks across all sections
• Bold formatting for UI elements
• Inline code for file names, URLs, and commands
• Grammar fixes and updated ms.date
• Updated Yeoman prompts to match current generator behavior

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 4da3c19:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/spfx/extensions/get-started/query-suggestion-tutorial-building.md	⚠️Warning	View	Details
docs/images/query-extension-yeoman.png	✅Succeeded	View

docs/spfx/extensions/get-started/query-suggestion-tutorial-building.md

• Line 159, Column 5: [Warning: file-not-found - See documentation] Invalid file link: '../../../images/query-extension-search-settings.png'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit fba429e:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/images/query-extension-yeoman.png	✅Succeeded	View
docs/spfx/extensions/get-started/query-suggestion-tutorial-building.md	✅Succeeded	View

For more details, please refer to the build report.