[PAN-2345] node permissioning controller

[macfarla]

PR description

Refactor NodeWhitelistController to NodeLocalConfigPermissioningController
Refactored NodePermissioningController to accept multiple providers and check all of them
Added to LocalConfigNodePermissioningController the notion of its own enode URL. The node will not add its own enode to the whitelist.

Fixed Issue(s)

fixes #PAN-2345

[lucassaldanha]

For the NodePermissioningControllerTest test, we need to ensure we have the different possible scenarios covered:

1. When using only local config permissioning
   • Should NOT check the SyncStatusPermissioningProvider
   • Should only delegate to the NodeLocalConfigPermissioningController (only one provider will be enabled)
2. When using SmartContract based permissioning (either standalone or in conjuction with local config)
   • If SyncStatusPermissioningProvider.isPermitted() returns false, communication is not permitted
   • If SyncStatusPermissioningProvider.isPermitted() returns true:
     • communication is permitted if every other provider returns true
     • communication is forbidden if any provider returns false

The current name of the test methods imply the the SyncStatusPermissioningProvider is always used. This shouldn't happen.

[lucassaldanha]

LGMT. Just some optional assertion suggestions.