Multiple port mapping failures in daemon unit tests logs (e.g., Test Conference and Test Conversation)

A long list of port mapping failures appears in the daemon unit test logs. This issue is likely related to enforceAvailableMappingsLimits() calling provisionNewMappings() even when there is no valid IGD. Additionally, provisionNewMappings() does not manage its failed mappings, they remain in the list instead of being removed. Consequently, at the end of the discovery phase _endIgdDiscovery(), the status is updated to failed and logged, even if it was already failed.