AnomalyType parsing vs Anomaly

Anomaly parser should be platform ignorant and simply build a small message informing the user what went wrong
AnomalyType (wip) should be platform dependent, build outer messages with cool platform features like click messages, probably delegate to the new interfacing boss in #10

Order of anomaly submit is like:

(where I is an object handling the input type of the node base and a handling final adapted type)

AnomalyParser -> (if on correct platform) -> AnomalyTypeParser -> MessageBoss -> Player
(if on incorrect platform) -> MessageBoss -> Player

Start with the AnomalyParser, AnomalyTypeParser, MessageBoss, and Player flow described in the issue, then read the referenced work in issue #10. Confirm how platform-dependent and platform-agnostic paths should differ. Done means the parser builds the basic error message while platform-specific outer messaging is separated as outlined.

Written by the indexing model from the issue text.