Fixed bug where id->misc->defines wasn't left behind properly after a
top level RXML parse if there had been another RXML parse pass earlier
This has possible compatibility impact in case a third party module
counts on that the id->misc->defines from the first and not the last
(non-nested) RXML parse pass is present at the end of the request.
Since several non-nested RXML passes are uncommon it's probably a rare
Also improved the request trace a bit to show what is being done with