Close more gaps between URL writing and parser sections

Three fixes align the writing grammar with the parser, addressing
divergences reported in #704:

* Introduce path-absolute-non-authority-URL string. Where scheme-relative
  and path-absolute were both offered as top-level alternatives, inputs
  starting with "//" could fall back to path-absolute when the
  scheme-relative form failed. This made foo://:80, foo://h@x,
  foo://h:8x, and //:80 (against https://, foo://, and file:// bases)
  incorrectly valid.

* Remove path-absolute-non-Windows-file-URL string. The parser accepts
  file://host/C:/demo and /C:/path against file://server/tmp/ without
  validation errors, so the grammar should too.

* Require U+0023 (#) in the opaque-path branch of
  relative-URL-with-fragment string. The empty string against foo:opaque
  was valid by the grammar but fails to parse.

Helps with #704.