docs: add WaveSpeedAI ComfyUI guide

[Leeon-Tang]

Summary

Adds a community tutorial for using WaveSpeedAI with Open WebUI through the existing ComfyUI image generation engine.

Changes

• Adds a WaveSpeedAI guide under Create & Edit Images
• Covers installing the WaveSpeedAI ComfyUI custom node
• Explains API key configuration through ComfyUI Settings, config.json, or WAVESPEED_API_KEY
• Shows how to export a WaveSpeedAI workflow in API format before uploading it to Open WebUI
• Adds node mapping notes and troubleshooting for common ComfyUI/Open WebUI setup issues
• Adds a local stylelint disable around the existing disclaimer-bar link selectors so the current CI stylelint rule passes without changing their visual styling

Validation

• npm run prettier:check
• npm run lint
• npm run stylelint
• npm run mdx-check
• npm run build

Note: npm run build still reports pre-existing broken-anchor warnings elsewhere in the docs, but the build succeeds and no warning references the new WaveSpeedAI page.

[pr-validator-bot]

ℹ️ Documentation PR Guidelines

👋 Welcome! This is an automated message posted on all new documentation PRs to help guide our contributors. Just because this comment appeared doesn't mean you have done anything wrong!

Please ensure you're using the correct branches:

Target branch (where you're merging TO):

• dev branch: For documentation related to upcoming Open WebUI releases (new features, new environment variables, anything dependent on unreleased versions and unreleased features/fixes/changes)
• main branch: For content that can go live immediately (fixes, tutorials, documentation not dependent on unreleased features)

Source branch (where you're merging FROM):

• If targeting dev, create your branch from your fork's dev branch
• If targeting main, create your branch from your fork's main branch
• ⚠️ Mismatched branches can and will result in unwanted file changes being included in your PR!

If your docs PR depends on a pending PR in open-webui/open-webui:

• Convert this PR to DRAFT mode!
• Link to the related main repo PR in your description for clarity
• We'll review both together once the PR on the main repo is merged

Please adjust your PR target branch, source branch, and/or draft status accordingly if needed.

[Classic298]

is this tested?