Add weatherzone.com.au to yellowlist

[ghostwords]

To unbreak weather-related images on the following websites:

• https://www.bluemts.com.au/weather-forecast/
• https://www.hawkesburyaustralia.com.au/weather-forecast/
• https://www.experiencesydneyaustralia.com/visitor-information/weather/

Privacy Badger debugging info (instructions):

**** ACTION_MAP for weatherzone

www.weatherzone.com.au {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "block",
  "nextUpdateTime": 1501904291446
}

weatherzone.com.au {
  "userAction": "",
  "dnt": false,
  "heuristicAction": "block",
  "nextUpdateTime": 0
}

**** SNITCH_MAP for weatherzone

weatherzone.com.au [
  "bluemts.com.au",
  "hawkesburyaustralia.com.au",
  "experiencesydneyaustralia.com"
]

The tracking that Privacy Badger sees comes from AWS "sticky sessions" load balancer cookies (the cookie info comes from Chrome's cookie details screen found under Settings > Advanced > Content settings > Cookies > Search cookies; here is the direct URL to the Cookies screen: chrome://settings/content/cookies):

Name: AWSELB
Content: B91D09251A9AEDA4A6E0B5D8E22294B3...7CAD2DC5BB63CA01BE7F37EA
Domain: www.weatherzone.com.au
Path: /
Send for: Any kind of connection
Accessible to script: Yes
Created: Tuesday, August 1, 2017 at 11:36:22 AM
Expires: Tuesday, August 1, 2017 at 12:36:22 PM

These cookies have a short expiration date (one hour). Should we treat them differently? This is related to session cookies, which came up in #1539.

[cowlicks]

I think the proper fix here is to include some calculation of the cookie duration in the heuristic. If their intent was to track, they would be setting longer expiration periods.

However this should be merged as a stopgap, with a follow up issue to remove it.