and make it possible to print the entire line of output if we see it

a specific order of the underlying datasrc SQLite3 query result, but it
doesn't appear to be the case for all systems.

(I made a couple of piggy-back small fix/cleanup: avoid unexpected exception
in an assert failure message for an empty (test) RRset; suppress log output
(by default))

Conflicts:
	src/lib/datasrc/database.cc
	src/lib/datasrc/tests/database_unittest.cc

Readded as it got lost in the merges somewhere.

Conflicts:
	src/bin/bind10/bind10_src.py.in

Conflicts:
	src/bin/bind10/bind10_src.py.in
	src/bin/bind10/tests/bind10_test.py.in

Conflicts:
	src/bin/bind10/bind10_messages.mes
	src/bin/bind10/bind10_src.py.in
	src/bin/bind10/tests/bind10_test.py.in

Conflicts:
	src/bin/bind10/bind10_src.py.in

Conflicts:
	ChangeLog

Which check it is started correctly on startup, not only on
reconfiguration.

Conflicts:
	src/bin/xfrin/tests/xfrin_test.py
	src/bin/xfrin/xfrin.py.in

to an existing entry)

hid the definition of uint32_t.  also, replaced an unused boost header file
(foreach) to a more relevant one (shared_ptr).
may be beyond a super-trivial level, but as an urgent care fix I'll push it
now.  it was confirmed on our solaris box.

complains about it.