Avoid a couple of InexactErrors in the IdDict code.

[maleadt]

Fixes #48097 (working around the issue).

On 1.9, kwarg calls use Base._tuple_unique_fieldtypes, which relies on IdDict. Normally that doesn't matter, because the method is marked @total_meta so the optimizer is free to use concrete evaluation to evaluate the function at compile time. However, with our GPU back-ends, Core.throw_inexacterror is replaced with an overlay method that does GPU-compatible exception reporting. That currently disables concrete evaluation, resulting in run-time calls to Base._tuple_unique_fieldtypes (and a whole lot of dynamic code following it).

To get things working in time for 1.9, just avoid throwing InexactErrors as part of IdDict operations. That results in the optimizer being able to concrete evaluate Base._tuple_unique_fieldtypes even in GPU compilation mode.

For 1.10, we probably need a better way of overriding methods without disabling concrete evaluation. Some GPU overrides should not disable these optimizations, e.g., if we override Base.sin with a version that uses hardware intrinsics we should still get to benefit from concrete evaluation (albeit using the original method). In other cases, like the Core.throw_inexacterror overlay here, it's not so clear what needs to happen.

[maleadt]

CI failures unrelated.