Fix fallbacks not being used in the launcher on 500 class errors

[VasilisThePikachu]

This is really the best way i can think of solving the issue from #252, a 500 is 100% something going wrong and the fallback needs to be attempted.

If you have better suggestion to make this more reliable please suggest it.

I think if both main and fallback 500 here the launcher will crash again though...

[PJB3005]

I think if both main and fallback 500 here the launcher will crash again though...

So uhm, you didn't test this?

[VasilisThePikachu]

I think if both main and fallback 500 here the launcher will crash again though...

So uhm, you didn't test this?

Admitibly yes until now (My internet had cut out the day you sent this comment and i forgot until now to actually respond)

The reason I did not test it is that this is "intended" (note the quotes) is because of this, this is the exception i screenshoted above.

SS14.Launcher/SS14.Launcher/HappyEyeballsHttp.cs

Lines 248 to 253 in 171b5d1

	if (successTask == null)
	{
	// We didn't get a single successful connection. Well heck.
	throw new AggregateException(
	allTasks.Where(x => x.IsFaulted).SelectMany(x => x.Exception!.InnerExceptions));
	}

Should this be causing a launcher crash... probably not.