Rework the Chromium cookie code

This fixes the same problem that existed in Firefox with cookies being flagged
as secure from JS contexts:
https://trac.torproject.org/projects/tor/ticket/7492

But actually in Chrome things were more severe, and cookies set in HTTP
(non-S) headers could be flagged as secure too!

Conflicts:
	chromium/manifest.json

Conflicts:
	chromium/manifest.json
[CHROME] Ignore port numbers when searching for rulesets

(and also when canonicalising hostnames)

Fixes https://trac.torproject.org/projects/tor/ticket/8413