Use config for the SensesField

[Larkinabout]

Intended to allow custom senses by editing CONFIG.DND5E.senses.

[Larkinabout]

I believe the only thing left to do is resolve MovementSensesConfig._preparePartContext, though I'm still not clear on how to do it. I'll keep trying to figure it out, but would be grateful for anyone's insight to speed me along.

[Larkinabout]

Note to remind that we may wish to also move group actor movement types into a types object for consistency, but for the moment I've handled it in movement-senses-config.mjs.

Also, would be useful to allow group movement to also be configurable. CONFIG.DND5E.vehicleTypes could be viable, but it includes space, which would need to be excluded by default in the various places where movement is determined. This would cause an issue if a user actually wants to add space as a movement type.

[arbron]

@Larkinabout It would be good to take the compendium changes out of this PR, we can handle them later and we'll want to make sure that the migrations in place are enough to keep compendium content working even if it doesn't have the new data layout (plus it makes it easier to review)

[Larkinabout]

@Larkinabout It would be good to take the compendium changes out of this PR, we can handle them later and we'll want to make sure that the migrations in place are enough to keep compendium content working even if it doesn't have the new data layout (plus it makes it easier to review)

Understandable, will sort soon.

[krbz999]

This probably also needs migrations for ActiveEffects. All AEs that modify system.attributes.senses.* should point at something different, or we just support the same deprecated property but point it elsewhere in the AE document class.