Fix ridiculous regex anchor mistake from 66137dffe
Unused import
Temporary CI workaround for RT#92226
Allow devcpan tests to pass by not considering SQLA 1.99_xx
Switch the bleadcpan test to 5.8.7
Centralize handling of refcount in DBIC::_Util
Rewire the leaktracer to store all refs by address, not by name

Also add better diagnostics during failure
Stop various CLONE-registries from growing indefinitely
Even saner diagnostics (view under diff -w)

Now that we no longer store signs of "ref X was here but GCed" there is no
point in "No leaks of X" pass()es either
Switch to a global symtable "classdata" visitor

This not only allows us to track anything global, not only CAG stuff
but also removes a bunch of workarounda from t/52leaks.t \o/
Now that we have the tools leak-track much more stuff when XS is there
Stop circref TODO based on RT#82942 from failing after changes in 96577657
Smoke 5.16.2 (ensure we are not affected by Encode leak) and bump latest 5.18
Do not track plain scalar refs on 5.17+ for the time being
Add extra operations to the heavy duty leaktrace scope

Fire all so-far-collected resultsets multiple times
Stop using precomputed SQLite testdb name, fix test-end bug in replicated.t

This was an... odd one. Originally the problem manifested as a classic
var-sub-sub closure problem, leading to $db_file being captured and tripping
a more involved testcase that is coming in a subsequent commit. However while
getting rid of the reference itself was easy, this led to the outer coderef
itself being "leaked out".

The reproducing oneliner is:

~$ perl -MScalar::Util=weaken -Mstrict -Mwarnings -e '
 sub foo {
   my $rv = sub { "wtf" }; return $rv;
 }

 my $should_be_gone;

 {
   $should_be_gone = foo();
   weaken ($should_be_gone);
 }

 warn $should_be_gone;  # why is this still defined@!%#$!$#
'

Various tools indicated that it is somehow attached to the PAD of the static
foo() sub, but I could not figure out *why* exactly this is happening, nor
how to properly list it: PadWalker's closed_over() shows nothing for foo()

Thus invoking doge on the whole shebang, and moving on. SUCH WTF, WOW!

Incientally changing things to use the current SQLite filename revealed
a bug in t/storage/replicated.t, which was never noticed as it only
resulted in annoying warnings under Win32 global destroy (test
teardown).
Fix long standing issue with resultset growth on repeated execution (GHPR#29)

The "save the SQLA argstack" dirty solution introduced in 975b573a actually
resulted in an infinitely growing nested data structure, containing the
history of *every* reinvocation of the resultset. Scale back the problematic
part, though this is still an interim workaround. A DQ-based stack should
make this much cleaner.
Massive incompatible change of ::BlockRunner internals

It was never documented as usable externally (though folks do use it, sigh)
This last set of changes settles the design for proper documentation and
opening up
Need some exceptions removed in 556c4fe6 when some optdeps are missing
Do not run the expensive test under PPerl/SppedyCGI