Inexor Flex reconnects to already running instances of Inexor Core

[aschaeffer]

By reconnecting to already running instances of Inexor Core allows server owners and developers to restart/update Inexor Flex while Inexor Core instances are still running. This improves the development process at the first place but also improves the runtime stability.

Goals

• Improve runtime stability / decrease downtimes (see note 1)
• Improve development efficiency

User Stories

• [ ] As a server owner I don't want to stop my Inexor Game Servers during updates of Inexor Flex
• [ ] As a developer I want to quickly test new features in Inexor Flex and the user interface by restarting Inexor Flex
• [ ] As a developer I want to switch the Inexor Flex profile at runtime

Inexor Flex

• [ ] For each instance in instances.toml check if port of the instance is in use
  • Port is already in use:
  • [ ] Connect to the already running instance
  • [x] Populate Inexor Tree of the instance with defaults
  • [ ] Pull Inexor Tree from Inexor Core to Inexor Flex
  • [ ] Force reload of the user interfaces
  • [ ] Attach stdout console
  • Port is not in use and autostart is activated for the instance:
  • [x] Start instance
  • [x] Connect to instance
  • [x] Populate Inexor Tree of the instance with defaults
  • [x] Push Inexor Tree from Inexor Flex to Inexor Core
  • [x] Attach stdout console

Notice

1. In the first step, the instance of Inexor Core may switch to paused state during restart of Inexor Flex, but the instance keeps the enet connection alive

[a-teammate]

Separate issue for the same for core? So we have nice debugging again for Core.