consider to backport https://github.com/dotnet/runtime/pull/113645 to release/v9.0?

[srxqds]

I found the #113645 pr fix the anr for disable concurrent GC dotnet/android#9365 (comment)

or how can we workaround if we want to disable concurrent gc.
@lateralusX

[srxqds]

and another detail confirmed from this dotnet/android#9937 (comment)
if we call unmanged callers only method or embed api wrapper with mono_thread_attach and mono_thread_detach
for example:

mono_thread_attach();
call unmanged callers only method  or embed api
mono_thread_detach();

it will cause anr problem?
I think it is safe because we detach the thread.

[srxqds]

the issuse #116275 seam solve two problem:

1. signal handler stackwalk bug in hybrid mode and fixed in [Mono]: Additional support for signal async safe stack-walks. #113645, but this pr not backport to release/v9.0
2. not emit safe point in the case [Mono]: Compiling AsyncStateMachine won't emit safepoints on specific loop pattern. #116275, it can workaround by call some api native api like Thread.Slepp(1).

but as the coment dotnet/android#9365 (comment) the problem 2 occured not releated with gc concurrent setting. so what caused this anr problem and how they fix it?