Migration to 4.6.0

In this version we've introduced methods for signaling if specific player belongs to control (and uses your existing ad logic) or to optimized (and uses Nefta dual track ad logic) group.

After you've determined in which group the player belongs and selecting corresponding ad logic, signal this decision to us via:

// https://github.com/Nefta-io/NeftaMAXAdapter-Unity/blob/main/Assets/AdDemo/AdDemoController.cs#L119

// if using wrapper, this is done automatically
NeftaAdapterEvents.SetInterstitialLogic(isOptimized);
NeftaAdapterEvents.SetRewardedLogic(isOptimized);

// https://github.com/Nefta-io/NeftaMAXAdapter/blob/main/MaxIntegration/ViewController.swift#L65

NeftaPlugin.SetInterstitialLogic(isOptimized: isOptimized)
NeftaPlugin.SetRewardedLogic(isOptimized: isOptimized)

// https://github.com/Nefta-io/NeftaMAXAdapter-Android/blob/main/MaxIntegration/src/main/java/com/nefta/max/MainActivity.java#L48

NeftaPlugin.SetInterstitialLogic(isOptimized);
NeftaPlugin.SetRewardedLogic(isOptimized);

Changed method signature for GetRetryDelayInSeconds which now also needs "adUnitId" parameter.