excluded place nodes outside parent boundaries from addresses

Changes slightly the logic which decides if a guessed places
(i.e. a place node) is included in an address: it will be
part of the address only if it is inside the next lower
available boundary. This fixes problematic cases where
neighbouring entities have additional admin levels.
gracefully fail if nodes from an address interpolation are missing
adapt distance heuristics for nodes

Include only those nodes that are closer than 1.5 times the distance
of the closest feature of the same address rank.
Merge remote-tracking branch 'lonvia/address-order'
Fix repeating lat twice in span instead of lat, lon.
Merge branch 'patch-1' of https://github.com/Firefishy/Nominatim
send place_rank in jsonv2 format
fail on error

- stop indexing if there is any other error than deadlock from the DB
- stop import if osm2pgsql or indexing fails
don't create index idx_placex_sector twice
places that cannot be part of an address still should get an address themselves
gitignore dynamically created files
import TIGER data into temporary table

Import TIGER data into a temporary table first that later replaces
the current location_property_tiger table. This way index creation
on the table can be delayed until after the import which should
speed up the import and result in significantly smaller indexes.

Also removed index on parent_place_id as it is covered by
idx_location_property_tiger_housenumber_parent_place_id.
make sure first of each address rank is used

get_addressdata should not really return duplicates but if there are
the first result will be the best one, so make sure that one is used