\.bat$
\.bkp$
\.css$
\.cur$
\.eot$
\.ico$
\.gif$
\.jpg$
\.png$
\.js$
\.pl$
\.svg$
\.ttf$
\.woff$
\.bat\?
\.bkp\?
\.css\?
\.cur\?
\.eot\?
\.ico\?
\.gif\?
\.jpg\?
\.png\?
\.js\?
\.pl\?
\.ttf\?
\.woff\?
\.svg\?
ukgwacnf
jsessionid

\.bat$
\.bkp$
\.css$
\.cur$
\.eot$
\.ico$
\.gif$
\.jpg$
\.png$
\.js$
\.pl$
\.svg$
\.ttf$
\.woff$
\.bat?
\.bkp?
\.css?
\.cur?
\.eot?
\.ico?
\.gif?
\.jpg?
\.png?
\.js?
\.pl?
\.ttf?
\.woff?
\.svg?
ukgwacnf
jsessionid

Fix escaping of '?' for strip_mappings.sh
Fix escaping of '?' for strip_mappings.sh

With basic regular expressions there is no need to escape '?', it's
only treated as a meta character if escaped, or run with `-E`.

```
   Basic vs Extended Regular Expressions
       In basic regular expressions the meta-characters ?, +, {, |, (, and ) lose their special meaning; instead use the backslashed versions \?, \+, \{, \|, \(, and \).
```

This was causing some URLs to be stripped that shouldn't be, eg

 - `\.pl\?` would match any instance of .p, as the l became optional

This most obviously affected URLs for `www.planningportal...`, but
would have affected prior URL mappings if the right combination
was in the URL (due to the .requirement, mostly in the domain part)
