Optimization of configuration reload in Portal
For now, at each request on Portal, we check configuration backend to get the latest cfgNum and update configuration cache if needed.
This put an heavy load on configuration backend when configuration is updated, because all portal threads wil try to update the cache.
We should modify this behavior so that configuration cache is not updated by portal, but by a reload mechanism as we have with the Handler.