Client/Server Interface

RMTC is a system process running through Python, however AI and similar tracking systems usually have the expectation to run remotely using a client/server architecture which lowers the bar for access. There have been some tests with flask/HTTP to validate that this will work with RMTC - however those tests are not usable as a true system.

To meet general expectations and expand the interface options - we should look to allow for a System to System interface abstraction so we can have a Client connect to an RMTC server for dispatching and managing inferences & training using a web interface.

Start by reviewing the existing Flask/HTTP tests mentioned in the issue and the current RMTC system-process interface. Clarify the client/server abstraction and its scope before implementing; done should mean a client can connect to an RMTC server to dispatch and manage inference and training.

Written by the indexing model from the issue text.