Damage sensors in 1.8.0 format aren't handled correctly

Partner Rank:

1

Partner Team Reporting:

Everbloom Studios

Verification builds:

1.13.0.2 (as described here)
1.13.0.1 (slightly different behavior, where no damage is filtered and a content log is issued)

Summary:

Some damage sensor components in the 1.8.0 format version don't properly work as expected.
Example of a damage sensor that doesn't work properly (using 1.8.0 format version):

"minecraft:damage_sensor": [
    {
        "filters": {
            "test": "is_family",
            "subject": "other",
            "value": "player"
        },
        "event": "set:charged",
        "deals_damage": false
    },
    {
        "deals_damage": false
    }
]

Impact:

This breaks lots of existing content that uses damage sensors with similar JSON structure, making the affected entities not receive nor react to damage. One piece of affected content is one that is all ready for release.

Repro Steps:

1. Create and join the provided world. Find the area labeled MCM-836
2. Punch the creeper multiple times.

Observed Results:

Nothing happens when you punch the creeper.

Expected Results:

With every punch, the creeper should toggle between charged and normal.

Screenshots/Videos attached: Yes/No

No.

Regression Builds:

1.12.0.28