Backport of #112469 to release/9.0-staging

/cc @kunalspathak

Customer Impact

• Customer reported
• Found internally

We were wrongly reporting certain registers has gc references which would lead the GC would interpret the values as them as valid object addresses and enumerate over them. This would lead to an undefined behavior or crash. Although it is a rare occurrence and certain events need to line up in place (method's register requirements in given method, trigger of GC at the instruction where wrong registers are tracked, etc.), it is still a potential issue because it can lead to fatal crash and diagnosing that crash would take an area expert (hard to root cause).

Regression

• Yes
• No

In #97910, we started inlining TLS access for NativeAOT for linux/arm64 and the issue was introduced since then.

Testing

The failing test was reverified and the asmdiffs were studied to make sure that we are reporting the gc references correctly.

Risk

Low. This optimization is present in our mainline for almost a year now and was found from our internal tool just recently.