[WFLY-3978] - PicketLink EAP 6.4 Issues

Improving usability, removing unnecessary services and reload state.
In the rollback case I don't think this is the actual rolled back model. Normally for a write attribute handler we only deal with the one attribute and use the value passed in, but since you seem to be using a few other attributes from the model, I don't think that will work when doing a rollback. So something like:

       final ModelNode identityProviderNode;
       if (!rollback) {
              identityProviderNode = context.readResource(EMPTY_ADDRESS, false).getModel();
       } else {
              Resource rc = ctx.getOriginalRootResource().navigate(pathAddress);
              identityProviderNode = rc.getModel();
       }