Removing of a disabled filter seems cached

Environment

• Browser and full version: Chrome 95.0.4638.54
• Extension using this toolkit: test-mv2
• Commit hash: 72f80240

Steps to reproduce

EWE.filters.add("||testpages.adblockplus.org/testfiles/header/$header=content-type=application/javascript")
EWE.filters.disable("||testpages.adblockplus.org/testfiles/header/$header=content-type=application/javascript")
EWE.filters.remove("||testpages.adblockplus.org/testfiles/header/$header=content-type=application/javascript")
EWE.filters.add("||testpages.adblockplus.org/testfiles/header/$header=content-type=application/javascript")
EWE.filters.getUserFilters();

Actual behavior

The filter returned is disabled.

Expected behavior

The filter returned is enabled. Since the filter has been removed, the expectation is that the new filter is actually enabled. This is what happens when the filter is added for the first time.

This issue was found here. That line is expected to change when this is fixed.