Change 403 user options/ handling

[gamebeaker]

reference: #1491, #1488, #1361
Added option to block URL.hostname from an 403 error URL.
This can reduce the ammount of errors an user has to skip if the images on the website are now 403 like on patreon.

Changed 403 handling for the user.
Old:

New:
Only one error page.

[dteviot]

@gamebeaker

Did you intend to leave these lines commented out?

WebToEpub/plugin/js/HttpClient.js

Lines 85 to 92 in 957d698

	/*
	if (confirm(chrome.i18n.getMessage("warning403ErrorResponse", new URL(response.url).hostname))) {
	// Open site
	window.open(new URL(response.url), "_blank").focus();
	alert(chrome.i18n.getMessage("wait403ErrorResponse", new URL(response.url).hostname));
	} else {
	// Do nothing!
	}*/

[gamebeaker]

@dteviot no i was debugging and forgot.

[gamebeaker]

@dteviot i pushed a clean up commit here:97a5a40
What should be the workflow if i want to push code?

1. Should i directly push it in https://github.com/dteviot/WebToEpub/tree/ExperimentalTabMode directly without a pull request
   Con:
   I think it is harder to keep track of changes if they get directly merged
   Pro:
   Only 2 Commits in commit history, example:
   
2. Create a branch in my fork and create a pull request for this fork in ExperimentalTabMode.
   Con:
   Creates 3 Commits in commit history even for small changes (parser), example:
   
   Pro:
   I feel like it is easier to keep track of changes especially if they are new functionality/ changes in the code (not parser)

[dteviot]

@gamebeaker

Do whichever you are more comfortable with. I'm good either way.

Also, thank you very much for your work.