Switch to Rust versions of libespm and libloadorder about libloot HOT 2 CLOSED

The API functions affected by load order caching are:

• GameInterface::LoadPlugins() (also called as part of GameInterface::SortPlugins())
• GameInterface::IsPluginActive()
• GameInterface::GetLoadOrder()
• GameInterface::SetLoadOrder()
• DatabaseInterface::EvalLists()
• DatabaseInterface::GetGeneralMessages() (if evaluating conditions)
• DatabaseInterface::GetPluginMetadata() (if evaluating conditions)
• DatabaseInterface::GetPluginUserMetadata() (if evaluating conditions)

Loading state in Game (which implements GameInterface) isn't a problem as it has access to the load order handler, but ApiDatabase (which implements DatabaseInterface) doesn't.

LoadPlugins() should always reload state itself, as it's an expensive operation that then caches active states.

The other methods (apart from EvalLists(), which can't reload state anyway) may be assumed to be quick getters operating on cached data, but clients may want to reload the state without reloading plugins or setting the load order, so there should be a new API function for doing so.

For LOOT's usage, it should be enough to rely on the reloading in LoadPlugins(), as plugins are always loaded before (re)initialising any other data.

from libloot.

Done as of d60d964

from libloot.