A State Machine implementation with configurable state transitions.
It maintains state decoupling, allowing it to scale and support multiple setups.

Setup/Definition logic:
- Create a State Machine.
- Create states.
- Set the SM initial state.
- Set the SM default behavior: Action to take if no map is found.
  (NULL specifies to remain in the same state)
- Map State & Result to the next State. (state, result, nextState)
  Receiving an event wile in state, triggers a state operation, resulting in a StateResult.
  SM State is changed to the nextState based on the result.

Operation:
- Usually called from a controller that receives events in an asynchronous mode.
  Usage example:
  State *state = sm->getCurrentState();
  sm->execEvent(state->evExist());
  // At this stage sm->getCurrentState() will return a new state.

The controller is serving the cards (devices) by providing them means
to register to the controller with their SM and giving each a unique id for communication.

regCard() is used for card registration.
run() is used for running the controller, usually in it's own task in an endless loop,
blocking on recv messages.

An UML and a README file have been added.