Add reforge optimizer setting for Hit/Expertise preference

[Saji-Saji]

This pull request introduces a new option to the ReforgeOptimizer that allows caster classes to prefer Hit Rating over Expertise Rating when suggesting reforges. This helps ensure that, when both stats are available as reforging options, Hit is prioritized, which is more relevant for caster classes. The option is enabled by default for all Mage specializations. Additionally, this seems to make reforging decisions faster when enabled for casters as it removes possible options.

Key changes:

Reforge logic improvements:

• Added a new preferHitOverExpertise option to ReforgeOptimizerOptions and implemented logic in ReforgeOptimizer to filter out Expertise reforges in favor of Hit reforges for items that don't natively have either stat. [1] [2] [3] [4]

Mage specialization updates:

• Enabled the new preferHitOverExpertise option by default for Arcane, Fire, and Frost Mage simulation UIs to improve reforge suggestions for caster gear. [1] [2] [3]

[1337LutZ]

Can we not bake this into the reforger itself instead of making it a boolean? Just checking for all caster specs

isCaster := character.Class == proto.Class_ClassMage ||
				character.Class == proto.Class_ClassWarlock ||
				character.Class == proto.Class_ClassPriest ||
				character.Spec == proto.Spec_SpecBalanceDruid ||
				character.Spec == proto.Spec_SpecRestorationDruid ||
				character.Spec == proto.Spec_SpecElementalShaman ||
				character.Spec == proto.Spec_SpecRestorationShaman ||
				character.Spec == proto.Spec_SpecHolyPaladin ||
				character.Spec == proto.Spec_SpecMistweaverMonk

(but then in JS)

[Saji-Saji]

Can we not bake this into the reforger itself instead of making it a boolean? Just checking for all caster specs

isCaster := character.Class == proto.Class_ClassMage ||
				character.Class == proto.Class_ClassWarlock ||
				character.Class == proto.Class_ClassPriest ||
				character.Spec == proto.Spec_SpecBalanceDruid ||
				character.Spec == proto.Spec_SpecRestorationDruid ||
				character.Spec == proto.Spec_SpecElementalShaman ||
				character.Spec == proto.Spec_SpecRestorationShaman ||
				character.Spec == proto.Spec_SpecHolyPaladin ||
				character.Spec == proto.Spec_SpecMistweaverMonk

(but then in JS)

Baked in for all caster specs, Hesitant if we should do this for Holy Paladin or Mistweaver, as they may want to actually use expertise at times? We don't exactly support it, but someone may be using it.

[1337LutZ]

Can we not bake this into the reforger itself instead of making it a boolean? Just checking for all caster specs

isCaster := character.Class == proto.Class_ClassMage ||
				character.Class == proto.Class_ClassWarlock ||
				character.Class == proto.Class_ClassPriest ||
				character.Spec == proto.Spec_SpecBalanceDruid ||
				character.Spec == proto.Spec_SpecRestorationDruid ||
				character.Spec == proto.Spec_SpecElementalShaman ||
				character.Spec == proto.Spec_SpecRestorationShaman ||
				character.Spec == proto.Spec_SpecHolyPaladin ||
				character.Spec == proto.Spec_SpecMistweaverMonk

(but then in JS)

Baked in for all caster specs, Hesitant if we should do this for Holy Paladin or Mistweaver, as they may want to actually use expertise at times? We don't exactly support it, but someone may be using it.

Yea I think you can leave those out indeed. As they can also proc RoRo since they are considered Melee. (need to change that still)