test: integration with slashingRegistryCoordinator

[8sunyuan]

Edge case fixed:
The AllocationManager has a try/catch in the deregisterFromOperatorSets implementation. This was put in place to allow operators to force deregister from an AVS. However this can lead to a weird state where an operator is registered in AVS contracts but deregistered from EigenLayer. Checks for this are added for forceDeregistration by the AVS to avoid reverts. In addition, AVSSync (updateOperatorsForQuorum, updateOperator) will now also include these operators to be force deregistered.

Refactored integration tests to only use the SlashingRegistryCoordinator and defines a OperatorSetUser contract.
The SlashingRegistryCoordinator and the Registry contracts do not depend on the ServiceManager base contract.
Interactions with the core protocol are integrated with UAM and setting the avsAccountIdentifier as the unique account identifier address for the AVS. For existing AVSs, this will be the address of your ServiceManager contract.

TODOs, could be implemented in followup PR

1. integration tests with the RegistryCoordinator and legacy quorums will require some fork integration testing refactor and testing the legacy interfaces. This is still a TODO that should be added.
2. Integration tests with slashing and allocations
   • Should test the following, allocate, register to AVS after meeting slashable stake threshold, slash operator, update stakes, expect operator to have been force deregistered
   • allocate, register to AVS meeting slashable stake threshold, create vetoeable slashing request, veto slash, expect operator magnitude and shares to be unchanged

[0xClandestine]

Some nits, looks good otherwise.