Connection interface

[Scretch9]

This change decouples the Point class from specific communication protocols and enables it to communicate with various endpoints through a standardized interface. The Point class now interacts with an object of type IPointToInterlockingConnection, which defines the necessary communication methods. This approach make the system more flexible, allowing the Point class to seamlessly integrate with different communication mechanisms in the future such as mocked connections for testing.

[rs22]

Thanks. I've left a few remarks. Let's define some tests for the new connection class.

[LeandroParisi]

Tried to fix the test issue without sucess.
IT seems to be a problem only on Linux, on my local machine (Linux) I run out of memory when I try to run it...
THere are some links of things we could do:
https://stackoverflow.com/questions/55070502/intermittent-build-break-with-msb4166-child-node-exited-prematurely-vs-15

https://stackoverflow.com/questions/7916687/error-msb4166-child-node-exited-prematurely-shutting-down

https://learn.microsoft.com/en-us/archive/blogs/msbuild/node-reuse-in-multiproc-msbuild

dotnet/msbuild#7145

https://github.com/eulynx-live/subsystems/actions/runs/7043163481/job/19168476653?pr=15

https://stackoverflow.com/questions/7916687/error-msb4166-child-node-exited-prematurely-shutting-down

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-build#msbuild

https://stackoverflow.com/questions/7916687/error-msb4166-child-node-exited-prematurely-shutting-down

dotnet/msbuild#1709

[rs22]

There was an infinite loop in Test_Default_Position.

Also recommended reading: https://learn.microsoft.com/en-us/dotnet/standard/parallel-programming/task-cancellation