feat(model): Add SuperADD VAND4.0 winning method

[alexriedel1]

📝 Description

Hello!
This adds the SuperADD as proposed in https://arxiv.org/abs/2605.14808 using the authors implementation https://github.com/LukasRoom/SuperADD

I made some minor changes to improve the memory consumption and runtime and to allow for batching during validation. Also the default image is set to 448 as 640 patches on the ViT H Super takes up extremely much memory.

I also removed all the "bells and whistles" like segmentation map post processing and training augmentations. The augmentations can easily be made with anomalibs datamodules and the segmentation map processing can be done manually if needed but only boost the score i guess.

With the default settings the model reaches:

MVTec AD2 Vial

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃        Test metric        ┃       DataLoader 0        ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│        image_AUROC        │    0.9995918273925781     │
│       image_F1Score       │    0.9756097793579102     │
│        pixel_AUROC        │    0.9501352906227112     │
│       pixel_F1Score       │     0.357709139585495     │
└───────────────────────────┴───────────────────────────┘

MVTec AD2 Wallplug

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃        Test metric        ┃       DataLoader 0        ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│        image_AUROC        │    0.5274074077606201     │
│       image_F1Score       │    0.5432098507881165     │
│        pixel_AUROC        │    0.9193798303604126     │
│       pixel_F1Score       │    0.4700793921947479     │
└───────────────────────────┴───────────────────────────┘

✨ Changes

Select what type of change your PR is:

• 🚀 New feature (non-breaking change which adds functionality)
• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🔄 Refactor (non-breaking change which refactors the code base)
• ⚡ Performance improvements
• 🎨 Style changes (code style/formatting)
• 🧪 Tests (adding/modifying tests)
• 📚 Documentation update
• 📦 Build system changes
• 🚧 CI/CD configuration
• 🔧 Chore (general maintenance)
• 🔒 Security update
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)

✅ Checklist

Before you submit your pull request, please make sure you have completed the following steps:

• 📚 I have made the necessary updates to the documentation (if applicable).
• 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).
• 🏷️ My PR title follows conventional commit format.

For more information about code review checklists, see the Code Review Checklist.