Fix for #821,822,823

[CollinChaffin]

Cross origin security blocking prevents TGS from initializing when it cannot complete favIcon operations. This requires Anonymous declaration of crossOrigin.

More info:
https://stackoverflow.com/questions/49503171/the-image-tag-with-crossorigin-anonymous-cant-load-success-from-s3
https://bugs.chromium.org/p/chromium/issues/detail?id=409090#c23
https://bugs.chromium.org/p/chromium/issues/detail?id=718352#c10

TODO: Consider (continued) refactoring of favIcon (and other critical component) error handling/logging particularily during TGS startup/init

[Jollfye]

Tested your commit, it appears to be working on the latest Chrome 73.0.3639.1 (Official Build) dev (64-bit), TGS initiates with no errors (and so I'm not getting bombarded with that "Disable developer mode extensions" Chrome security message on every restart), all tabs with correct paled favicons after load, good. Tab suspending works, only just noticed one error when suspended new google.com tab for the first time, when donation notification arrived at the bottom left corner it was with no urled images, just text (see screeny), and this "new" error I saw in extension errors after:

Also Session management still looks like this as described in my issue #822 and throws the same error with '+' click:

So the help of @deanoemcke is still needed here.

[CollinChaffin]

That error is a totally different issue that I'll let @deanoemcke address I'm surprised to see new commits and not even a comment on this PR or the several open issues it fixes. I'm not tagged an official contributor so I could not commit direct or would have so hopefully Dean will at least acknowledge the contribution and tell me if it's okay or what exactly the issue is preventing commit.

EDIT: Understand for over 10 days NO commit in master has even fully initialized enough to suspend tabs on at least half the systems I test it on - so I jumped after 10 days to apply a tested fix that gets TGS up and running I've been running my fork with this commit 24/7 since without a single noticeable issue (other than the totally separate more cosmetic errors still needing addressing). You simply were not seeing these other errors before @Jollfye because TGS was SO broken it wouldn't init far enough to even get to these others. :)

[deanoemcke]

@CollinChaffin thanks so much for this. Sorry, I've been away on holiday so only found out about this last night. Also, all my chrome 'dev' testing is done on Canary, so I'm a bit surprised that this only appears in the Dev channel. I assumed that Canary would also have these changes?

I will follow up this PR with some cleanup of the init error handling code as you suggested.

@Jollfye I'm investigating your two issues now and will push some fixes soon.

Thanks everyone for all the debugging. It's been invaluable.

[deanoemcke]

@Jollfye i have fixed the donate buttons issue.
for the session management issue, it appears that it's specific to your particular session. are you comfortable giving me an export of the session that's causing you issues?

you can always try updating and testing the latest version first if you'd prefer to see if it's magically been fixed first..

[Jollfye]

@deanoemcke I updated TGS to the latest 158 build, donate buttons confirm fixed, about session management, sent u an email.