Improve local connection

[Neylix]

Description

Since we have a node view in the bootstrap that is not inserted into the P2P MemTable, we cannot rely on the MemTable field availability_history to know if the node is currently connected or not.

So I implemented a new ets table managed by the ConnectionSupervisor and Connection module to store the current connection state of a node. So we don't rely on other thing that just the connection itself to determine if a node is connected

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Unit test on connected? function

Running node connecting and stopping them

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[bchamagne]

Tested with 3 nodes:

• initial node ✔️
• new node ✔️
• node restart quick ✔️
• node was stopped for multiple summary ✔️
• node reset from scratch ✔️