[BUG] beacons module do not load if the first master in multimaster list is not reachable when minion starts

Description
I created a custom beacon module and noticed that in my Windows and Linux minions, which are set using multimaster list, if the first master in the list is not reachable/available when the minion starts, the beacon module does not load, despite the second master being available and the minion responding to this master.

Setup
Set minion in multimaster (active/active), create and deploy a custom beacon module, sync/provision the module to the Windows minion, stop the minion, stop the master service on the first master, start the minion service, check the minion log, despite the minion connected to the second master, the beacon module is not loaded.

This can be workaround by using the minion config option beacons_before_connect: True. But maybe not ideal in all cases.

I think the beacon module should load if any of the masters is reachable.

Start by tracing minion startup handling for the multimaster list and the beacons_before_connect option, then reproduce the setup with the first master stopped and the second available. Done means a custom beacon module loads when any configured master is reachable, on both Windows and Linux minions, without requiring the workaround.