* y/go:
  go/zodb/zodbtools/dump: Don't use goto

Tomáš Peterka noticed that gotos in dump.go are not actually needed because
the same functionality could be achieved with defer in more clean and
structured way.

Do it.

This brings ~ 5% performance hit

	name        old time/op  new time/op  delta
	ZodbDump-4   148µs ± 1%   155µs ± 2%  +4.69%  (p=0.000 n=9+10)

because defer implementation is currently not great
(https://github.com/golang/go/issues/14939)

If we absolutely need those 5% back it could be worked around similar to
e.g. FileStorage.Load:

https://lab.nexedi.com/kirr/neo/blob/6faed528/go/zodb/storage/fs1/filestorage.go#L133
https://lab.nexedi.com/kirr/neo/blob/6faed528/go/zodb/storage/fs1/filestorage.go#L141

/suggested-by @katomaso

NEO 1.9

* tag 'v1.9':
  Release version 1.9
  master: fix resumption of backup replication (internal or not)
  master: fix/simplify generation of TID
  master: fix possible failure when reading data in a backup cluster with replicas

For both current backends (SQLite and fs1) there is currently a problem
of working with UTF-8 filenames if opening is handled via urls. For
example if backend string is

	sqlite://neo.sqlite·P1-1

after parsing as URL and further reassembled as string it will be

	neo.sqlite%C2%B7P1-1

with then errors like

	neo.sqlite%C2%B7P1-1: open: unable to open database file

showing.

Since storage backends primarily work with local files it makes sense
not to play raw url reassembly games and just pass raw strings to
backends for open.

SQLite uri processing is still possible, via e.g.

	sqlite://file:filepath?param=value,...

See

	https://www.sqlite.org/c3ref/open.html	and
	https://www.sqlite.org/uri.html

for details.