Use smart pointers when storing stuff in the engine specific

With the EngineStorageIface added (MB-49071), we can now store more complex types in the engine specific, not just raw pointers. It would be nice if we could migrate entirely off storing T* and use unique_ptr/shared_ptr instead where possible, particularly in RangeScans.

Manifest in Collections::Manager::update was done in MB-54032.