feat(ui): add Generate tab Upscale controls

[AsuraAce]

Summary

This PR adds Generate-tab Upscale controls backed by the existing High Resolution Fix graph path.

It includes:

• a Generate-tab Upscale accordion with Latent and Upscale Model methods
• graph generation for latent HRF and model-based upscaling/refinement, including tiled VAE decode for the final latent decode
• model-family gating so Generate Upscale is visible/applied only for supported SD1.5 and SDXL bases
• preservation of hidden Upscale settings when users temporarily switch to unsupported model families
• metadata and recall support for HRF settings, refinement model, and dedicated HRF LoRAs
• Recall Parameters behavior that recalls the base generation size and leaves final output dimensions to Image Details
• UI polish for disabled-but-configurable Upscale settings and grouped refinement model selection

The main user impact is that Generate users can configure an upscale/refinement pass directly from the Generate tab, then recall/remix images using the original base generation dimensions plus the saved Upscale settings.

View screenshots

---

Related Issues / Discussions

N/A

QA Instructions

Focused automated checks run locally:

pnpm vitest --run src/features/nodes/util/graph/generation/addHighResFix.test.ts src/features/gallery/components/ImageMetadataViewer/ImageMetadataActions.test.tsx src/features/metadata/parsing.test.ts src/features/metadata/parsing.test.tsx src/features/controlLayers/store/paramsSlice.test.ts src/features/queue/store/readiness.test.ts
pnpm lint:tsc
pnpm lint:eslint
pnpm lint:prettier
git diff --check

Manual smoke coverage performed locally:

• Generate tab Upscale settings render while disabled and preserve configured values when enabled
• Latent HRF uses tiled final decode and avoids the previous VRAM issue
• Upscale Model HRF generates and metadata recall uses the base generation size
• Recall Parameters list the HRF refinement model and dedicated HRF LoRAs
• Unsupported model families hide/ignore stale Upscale settings without clearing them
• Generation queue smoke test passed with a single active backend for the Invoke root

Merge Plan

No special merge sequencing is required. This touches persisted Generate params and includes the corresponding migration/test coverage.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (not applicable)
• Updated What's New copy (not applicable)

[AsuraAce]

I found one more support-scope issue while smoke testing: latent Upscale is currently exposed for non-SD model families like ANIMA. I’m moving this back to draft briefly to tighten supported model gating before review.