Fields "last_event_id" and "last_received_event_id" should not be part of the module configuration

[manuelselbach]

It turned out, that the fields "last_event_id" and "last_received_event_id" inside of table "tx_fourallportal_domain_model_module" holding a state depending of an environment. If such IDs are deployed, this might end up in a not up2date event and with a sync some events are applied again.

Suggestion from my side: move those fields into the TYPO3 registry and store the IDs with a hash of the combination of the module and server configuration. With this, the state will always be saved just for the environment and not part of the configuration.