[Defaulttype] TypeInfoRegistry: Fix crash at exit in TypeInfoRegistry deleter

[fredroy]

Fix Issue #6182

By Claude:

The root cause is the storage deleter in TypeInfoRegistry::getStorage(), which calls delete info on every stored pointer except NoTypeInfo::Get(). However the registry holds two kinds of pointers:

• NameOnlyTypeInfo objects it allocates itself with new (in AllocateNewTypeId) ‚ genuinely heap-owned.
• Pointers registered via Set(), e.g. DataTypeInfoDynamicWrapper<...>::get() (and VirtualTypeInfo<T>::get() used by Data::getValueTypeInfo()), which return function-local statics.

Deleting those static-storage singletons is undefined behavior (invaliddelete + double destruction, since the statics also self-destruct via their own atexit handlers), which triggers the trap. The deleter already special-cased NoTypeInfo::Get() as a singleton but missed that every info registered via Set() is a singleton too.

Fix: Only free what the registry actually allocates:

• getStorage() now holds non-owning borrowed pointers (no delete-all deleter).
• A separate getOwnedStorage() (vector<unique_ptr<const AbstractTypeInfo>>)
  owns the NameOnlyTypeInfo objects created in AllocateNewTypeId.

This preserves the leak-free intent of the original deleter (#4838) while never deleting the borrowed static singletons registered through Set().

---

By submitting this pull request, I acknowledge that
I have read, understand, and agree SOFA Developer Certificate of Origin (DCO).

---

Reviewers will merge this pull-request only if

• it builds with SUCCESS for all platforms on the CI.
• it does not generate new warnings.
• it does not generate new unit test failures.
• it does not generate new scene test failures.
• it does not break API compatibility.
• it is more than 1 week old (or has fast-merge label).