feat: Initial implementation of Melee damage as a stat on weapons (for glaives)

[FlaminSarge]

Adds melee and pve_melee to FiringData
Adds melee and pve_melee (with default 0) to SubFamJson
Adds melee_dmg_scale to DamageModifierResponse
Add melee_dmg to DamageProfile

Close To Melee, Vexcalibur/Winterbite perks, updated empowering damage modifiers, Triton Vice, Wormgod Caress, Winter's Guile, and Banner of War are all handled.

The intended UI experience is that Melee damage is only shown if it is nonzero for a weapon's damage profile. We could also go with it only being shown if it is not equal to a Guardian's default punch damage, for the sake of showing it when One-Two Punch and other melee buffs have been proc'd, but then the melee damage indicator would no longer be tied to the weapon being displayed. Limiting it to Glaives (for now) keeps it relevant to the current weapon's damage profile.

Sources:
Glaive interaction spreadsheet: https://docs.google.com/spreadsheets/d/1FT-BL6UA6ntNEN7_btqwlfJaPYTAeIFvlhpkvWHTajc/edit?usp=sharing
Damage stacking spreadsheet: https://docs.google.com/spreadsheets/d/1i1KUwgVkd8qhwYj481gkV9sZNJQCE-C3Q-dpQutPCi4/edit#gid=242217075
light.gg
amoral_support and oni_black_mage's testing
Mossy's spreadsheet: https://docs.google.com/spreadsheets/d/1b57Hb8m1L3daFfUckQQqvvN6VOpD03KEssvQLMFpC5I/

[FlaminSarge]

I need updated data for weapon_formulas, as some of it is definitely not correct.

[oh-yes-0-fps]

I like this, more ergonomic perk creation is something that should be pursued like this

[FlaminSarge]

I like this, more ergonomic perk creation is something that should be pursued like this

If needed I can pull this out into its own PR as well to reduce how many changes are in this PR.

[FlaminSarge]

I went ahead and put these changes in #112, after which I'll rebase this

[oh-yes-0-fps]

It would have been great if the ..Default::default for all modifier response construction was a separate pr as it feels orthogonal to the adding of glaives. I understand it happened because you made a breaking change and if you were gonna fix all the errors might as well do it, I've done that exact thing before.

[oh-yes-0-fps]

I would almost say just pulling 11393bc into a separate pr would be worth it to an extent, also this may be out of the scope right now but Weapon::get_damage_profile(bool) return type should definetly be turned into a struct and i don't fullt remember why i didn't make it one to begin with.

[FlaminSarge]

I would almost say just pulling 11393bc into a separate pr would be worth it to an extent, also this may be out of the scope right now but Weapon::get_damage_profile(bool) return type should definetly be turned into a struct and i don't fullt remember why i didn't make it one to begin with.

Moved the Default::default changes into #107, will need to rebase this after that gets merged.
Also #108 for DamageProfile

[FlaminSarge]

Last thing remaining is Vexcalibur ranged damage numbers and then this should be good to go