FSLogix Redirections Using Wildcards

Does FSL recognize wildcards? Trying to catch when a new Chrome profile is created (we've seen some users have "Profile 1", some have "Profile 4", etc) What we currently have to catch profile names if they aren't under Default:

	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\Cache</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\Code Cache\js</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\DawnCache\js</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\GPUCache</Exclude>
  	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\JumpListIcons</Exclude>
   	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\JumpListIconsRecentClosed</Exclude>
   	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\JumpListIconsOld</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\Service Worker\CacheStorage</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile 1\Service Worker\ScriptCache</Exclude>

Would this be possible and supported by FSL?

	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\Cache</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\Code Cache\js</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\DawnCache\js</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\GPUCache</Exclude>
  	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\JumpListIcons</Exclude>
   	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\JumpListIconsRecentClosed</Exclude>
   	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\JumpListIconsOld</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\Service Worker\CacheStorage</Exclude>
	<Exclude Copy="0">AppData\Local\Google\Chrome\User Data\Profile*\Service Worker\ScriptCache</Exclude>