Added startup, shutdown methods to IpSocket and added startup as a re…

[LeStarch]

…try step

Originating Project/Creator
Affected Component
Affected Architectures(s)
Related Issue(s)
Has Unit Tests (y/n)
Builds Without Errors (y/n)
Unit Tests Pass (y/n)
Documentation Included (y/n)

---

Change Description

Briefly, fixes the TcpServer such that it will retry both the listen and accept steps not just the accept step.

More in-depth:

Sockets originally were implemented with open and close steps. However, some sockets (like the TcpServer) needed to have startup and showdown steps too. This was patched in directly to this socket, which meant that retries on generic sockets didn't handle this case.

This PR adds:

1. startup and shutdown methods generically to all sockets (with the default being no-op)
2. isStarted method to check status
3. Retry start up in the read loop if not started.

[LeStarch]

Possible issues:

1. Inconsistent use of this->getSocketHandler()->[[ action ]] and this->[[ action]] in SocketReadTask
2. No check for isStarted in socket read thread loop

[LeStarch]

This code works. Tested with:

nc -l 50000
fprime-gds --ip-client

Then killed nc. Waited for socket wait then the server socket reconnected!

[thomas-bc]

Looks good to me!
Couple of notes:

• We're going to want to remove the explicit calls to startup/shutdown in the fprime-tools cookiecutters - also in references/tutorials if we switched any to be TcpServers already?
• Browsing through the code while reviewing this, I noticed that all references to Berkeley sockets in the codebase are misspelled (missing an "e" in Berkeley, e.g. here). This PR could be a good opportunity to fix that with a quick search/replace?

[thomas-bc]

REMINDER

Please merge nasa/fprime-tools#168 after this has been merged