AAE keeps track of non-cluster hosts

[mcesaro]

Hi @aramallo, I noticed also the even after re-booting all the components in the cluster, the AAE is still consideringnodes that are not supposed to be in the cluster. In the example, the peer test@max-a5 was supposed to be short lived for testing purposes:

=NOTICE REPORT==== 25-Oct-2023::15:58:12.250006 ===
    description: AAE exchange starting
    peer: 'test@max-a5'
    partitions: [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15]
=NOTICE REPORT==== 25-Oct-2023::15:58:12.250418 ===
    reason: nodedown
    description: AAE Exchange aborting, peer node down
    peer: 'test@max-a5'
=NOTICE REPORT==== 25-Oct-2023::15:58:12.263259 ===
    description: AAE exchange finished
    peer: 'test@max-a5'
    summary: #{skipped => [0]}
=NOTICE REPORT==== 25-Oct-2023::15:58:12.622372 ===
    description: AAE exchange starting
    peer: 'ska@max-a5'
    partitions: [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15]

However, after a few hours that test is gone, partisan keeps including it in the AAE.

[aramallo]

@mcesaro is this still happening in the latest version? Thanks