ObjectSpace.dump: handle Module#set_temporary_name

[Bug #20892]

Until the introduction of that method, it was impossible for a
Module name not to be valid JSON, hence it wasn't going through
the slower escaping function.

This assumption no longer hold.

Co-authored-by: Jean Boussier <jean.boussier@gmail.com>

This seems to happen only on VisualStudio:
https://github.com/ruby/ruby/actions/runs/7130917319/job/19418375386

It fails relatively frequently. Nobody seems actively working on it, so
let's skip it until somebody starts working on it.

Not all `ID` have an associated string.

Fixes a SEGFAULT in ObjectSpace.dump_all spec.

This reverts commit 9a62fd3cbae2ebb60e2f9cad782af1ad18db4319.

Since the callback defined in the objspace module might give up the GVL,
we need to make sure the right cr->mfd value is set back after the GVL
is re-obtained.

Some code out there blind calls `force_encoding` without checking
what the original encoding was, which clears the coderange uselessly.

If the String is big, it can be a rather costly mistake.

For instance the `rack-utf8_sanitizer` gem does this on request
bodies.

super() uses 0 as mid for its callinfo, so we need to check for that to
avoid a segfault when using dump_all.

Co-authored-by: Alan Wu <alansi.xingwu@shopify.com>

The address of objects can't be assumed since a later object may be
allocate in a swept slot.

Ensure that the frozen string is promoted to the old generation by
running the GC 4 times.