refactor: centralize model requirements logic per Issue #66

[Ref34t]

Summary

Implements Issue #66 by centralizing model requirements logic into the ModelRequirements class, improving separation of concerns between core API components and model discovery functionality.

Changes Made

• Move methods to a centralized location:

• ModelConfig::toRequiredOptions() → ModelRequirements::fromPromptData()

• ModelMetadata::meetsRequirements() → ModelRequirements::areMetBy()

• Remove PromptBuilder::getModelRequirements() method per issue requirements

• Update call sites:

• PromptBuilder now calls ModelRequirements::fromPromptData() directly

• ProviderRegistry now calls ModelRequirements::areMetBy()

• Clean up data holder classes:

• ModelConfig and ModelMetadata are now pure data holders

• Removed unused optimization maps from ModelMetadata

• Add comprehensive tests:

• 4 new tests for areMetBy() method (matching, missing capability, unsupported values, empty requirements)

• 4 new tests for fromPromptData() method (text generation, chat history, multimodal input, config options)

Architecture Impact

Improved separation of concerns: Core API components no longer depend on model discovery
Single Responsibility: ModelRequirements handles all requirements analysis

Fixes #66

[Ref34t]

@felixarntz The refractor is ready for review, in your hands

[felixarntz]

@Ref34t Just spotting this has merge conflicts - would you be able to resolve these please?

[Ref34t]

@felixarntz will tackle it today sure

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @mohamed.khaled@9hdigital.com.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: mohamed.khaled@9hdigital.com.

Co-authored-by: felixarntz <flixos90@git.wordpress.org>
Co-authored-by: Ref34t <mokhaled@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Ref34t]

@felixarntz The merge conflicts have been resolved. kindly review now 🥇

[felixarntz]

@Ref34t This looks like a solid start!

There are a few areas where maintaining the original logic would be preferable from a performance and architecture perspective. Likely because that's not the case, there are currently a few problems that need to be addressed either way.

[felixarntz]

@Ref34t This looks excellent - thank you for the iterations!