do a stronger dword CAS check for -latomic in autopkgtests

Some architecture+toolchain combinations can happily compile libatomic-free
operations up to a double-word compare-and-swap. When compiling a checker on
such platforms often the only undefined symbols you see are those relating to
_16, hence a uint64_t atomic load would spuriously pass the previous test.