Network connection issues, retries, and user experience

Network timeouts or connectivity issues currently manifest in myriad fashions and during file/publish operations can raise non-user-facing errors and mangled pipeline operations. Rather than selectively creating defensive fallbacks in the arbitrary places where these issues happen in operations, the entire pipeline should create a more global ayon_api solution where we have connection retries with exponential fallbacks, and upon final failure raise a dialog explaining network or connectivity issues and instruct the user to try again in 5-10 minutes, or if this persists check their network connection, or if that does not work, to contact pipeline engineering.