Description

This is another approach to the PR #13226

The issue:
Currently custom filters can not be applied to tokens, that are actually strings, like {dwc=slot-name}, because the current code does not execute ContactFiltersEvaluateEvent in that case, but replaces tokens with an empty string.

📋 Steps to test this PR:

1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs here)
2. Install the bundle https://github.com/Leuchtfeuer/mautic-DwcDeviceType-bundle , applying the PR [MTC-6662] Change DWC filter "Device Type" to work without core patch Leuchtfeuer/mautic-DwcDeviceType-bundle#4 and ignoring the patch note about the Enhances filters evaluation for DWCs  #13226
3. Go to "Dynamic content" and create a non-campaign slot for desktop devices:
   
   
4. Also create a non-campaign for non-desktop devices:
   
   
5. Create a page with both types of dynamic content: the HTML data-slot="dwc" and "inline text DWC" {dwc=slot-name}
   
   

<div data-slot="dwc" data-param-slot-name="landing_desktop_slot">
  <h1>Default web content for desktop.
  </h1>
</div>
<div data-slot="dwc" data-param-slot-name="landing_mobile_slot">
  <h1>Default web content for mobile
  </h1>
</div>

6. Check the resulting page in incognito mode, or another browser contains both "desktop" slots (or non-desktop, if you are testing on mobile). Example for a desktop:
   

If the PR is not applied the result is following:

7. Check the contact event log (you should enable anonymous contacts in the list to see new results):
   On the screenshot below the first entry (3 rows in the bottom) are log entries when the PR is active, and the rest (last four entries) are when the PR is not active.
   

8. You could also create additional slots to check if the previous functionality works as expected.