identities.IterateMalicious doesn't handle equivocation set for V2 ATXs correctly

[ivan4th]

Description

The identities.IterateMalicious doesn't check for married ATXs and thus yields the different set of malicious identities that you would get from going over every identity and calling identity.IsMalicious() for it, checking for true.
identities.IterateMalicious is used during warmup.
Related code:

go-spacemesh/sql/identities/identities.go

Lines 84 to 85 in 5091028

	"select (select count(*) from identities where proof is not null) as total, "+
	"pubkey from identities where proof is not null", nil, dec); err != nil {

Expected Behavior

identities.IsMalicious should handle equivocation sets correctly.