Core: Consolidate typed container logic with type_info.h

[Repiteo]

• Helps address [TRACKER] Compile time issues caused by excessive includes #111218
• Supersedes Core: Cleanup Array/Dictionary implementation #100953
• Supersedes Core: Migrate typed container logic #96741
• Supersedes Add new type_info properties to detect & identify Variant types #88567

The recent merge of #111561 enabled me to revisit this idea of simplifying typed container include logic, as that turned out to be the missing link in making everything else work! Instead of having to jump through hoops of dependency chains, type_info.h already has all the information it needs to declare relevant typing metadata for TypedArray and TypedDictionary.

The primary difference in this implementation compared to before is how the implementation is all handled in type_info.h now, instead of variant.h. This makes more sense logistically, as the typing metadata already exists in that context & could be safely reused. Because the information can be safely parsed ahead of time, the need for dedicated macros is completely gone: all typed containers can rely on a single implementation that covers all use-cases!

This entirely purges any attempted "bonus" codestyle changes/fixes from the original PR attempt: this attempts as atomic of a conversion as possible. As such, instead of removing the typed container headers entirely, they're now simple stub files. Miraculously, there was exactly one file where an additional include was required; everything else happens to utilize type_info.h transitively, which is a silver-lining of our current #include issues. A future PR focused entirely on stylistic changes can remove those headers outright & any references to them.

[Ivorforce]

Overall, this looks like a nice consolidation of logic. But I have two concerns:

• Why declare TypedDictionary when another file has to be included to get its definitions? Why not just declare it there? If we do it like this, trying to use TypedDictionary when not including type_info will error with difficult to understand messages.
• Why declare in type_info.h? Why not declare in typed_dictionary.hand includetype_info.h? Having the "internal" stuff shared across TypedArrayandTypedDictionarymakes sense to me, but not having theTypedArrayandTypedDictionary` definitions themselves there.

[Repiteo]

Thinking about it more, those two concerns were from when this was originally implemented in variant.h, which would've naturally overlapped with any base Array/Dictionary invokations. That's no longer the case, so keeping them in dedicated files should be fine after all.