Stakes not being considered as "active" by TACoChildApplication after being outgoing nodes on a handover

[manumonti]

• nucypher-porter has an endpoint (get_ursulas) to get a random bucket of nodes. This is used when we want to start a new ritual. nucypher-porter calls a TACoChildApplication function called getActiveStakingProviders().
• DKG heartbeats script also uses this TACoChildApplication function to know which nodes are active so it can generate the DKGs cohorts for the round.
• This contract function, check what is the eligibleStake of every staking provider address.
• When a handover is run, the finalizeHandover() function set the release boolean of the departing node to true.
• getActiveStakingProvider will check if this is set for every staking provider address, and if it is true, that address will not be returned by the function.
• This means that nucypher-porter get_ursulas() and DKG heartbeats script will not consider the nodes that were departing nodes on some handover. So they will be included neither on new rituals nor DKG heartbeats. They are not considered active even if these stakers continued running the node and staking.