Router handling of deleted agent configurations

When using the HttpBidderInterface, the user has to "manually" push the agent configuration to the ACS through the correct REST call.

When one wants to stop the traffic from being sent to the bidder (let's say a python bidder), one must remove the configuration from the ACS through the REST interface.
The router was not correctly handling configurations that were removed. The agent still was in memory and the configuration. This patch removes the agent from the internal
storage table of the router and removes the config from the filters as well so that a deleted configuration won't be a "potential bidder" anymore.