Fixed #23794 - FieldDoesNotExist error in migration with deleted fields and unique_together constraint

The code in `check_dependency` is too specific. For instance the `any` function for `operation.unique_together=set([])` always returned `False` which caused the bug to happen. This PR contains following changes:
* added test case for this bug
* added simplified condition

https://code.djangoproject.com/ticket/23794
I included the `any()` call to prevent problems with `RenameField` operations that that involve a field that's in an `foo_together`. Turns out, the `RenameField` handles the state changes itself. No need to check for it here.