[bug]: Model Manager imports Wan2.2-A14B VAE (single file) from local drive as an Anima VAE not available for Wan2.2

### Is there an existing issue for this problem?

- [x] I have searched the existing issues

### Install method

Invoke's Launcher

### Operating system

Windows

### GPU vendor

Nvidia (CUDA)

### GPU model

RTX 5090 Laptop GPU

### GPU VRAM

24GB

### Version number

v6.14.0-RC2

### Browser

Edge

### System Information

_No response_

### What happened

Imported Wan2.2-A14B-T2V-I2V VAE model from my local drive in Model Manager for use with Wan2.2 I2V workflow. But the model manager classified the VAE as an Anima VAE and not available for selection in the dropdown menu for Wan2.2 workflow.

### What you expected to happen

I expected it to be classified as a Wan2.2 VAE, which it is.

### How to reproduce the problem

idk. Start trying to import single file models, ditch diffusers format models. Try with all available Qwen Image, Wan2.1 and Wan2.2 single file VAE models.

### Additional context

Note: Similar problem happens with nearly all Qwen-Image VAE and Wan2.1 VAE. The problem is now observed for Wan2.2 VAE as well. In all cases the model manager classifies those as Anima VAE and hides them from the dropdown menu for VAE selection. It seems the Model Manager design is faulty and/or extremely poor. It likes to be given diffusers format models. I hate diffusers format models and prefer to use single file format models always.

### Discord username

_No response_