fix(log,config) : Using default log levels if config file doesn't exist

User were met with initialize errors when log level configs don't exist.
It is caused by uncaught exceptions during file reading, leading to EOSManager.Init ceasing to complete.
This fix catches those exceptions and continues the init using default log levels

Author: arthur740212

com.playeveryware.eos/Runtime/Core/EOSManager.cs

@@ -752,6 +752,12 @@ private void InitializeLogLevels()
             {
                 var logLevelList = LogLevelUtility.LogLevelList;
 
+                if (logLevelList == null)
+                {
+                    SetLogLevel(LogCategory.AllCategories, LogLevel.Info);
+                    return;
+
+                }
                 for (int logCategoryIndex = 0; logCategoryIndex < logLevelList.Count; logCategoryIndex++)
                 {
                     SetLogLevel((LogCategory)logCategoryIndex, logLevelList[logCategoryIndex]);

com.playeveryware.eos/Runtime/Core/Utility/LogLevelUtility.cs

@@ -43,7 +43,22 @@ public static List<LogLevel> LogLevelList
         {
             get
             {
-                LogLevelConfig logLevelConfig = Config.Get<LogLevelConfig>();
+                LogLevelConfig logLevelConfig = null;
+                try
+                {
+                    logLevelConfig = Config.Get<LogLevelConfig>();
+                }
+                catch (System.IO.FileNotFoundException)
+                {
+                    Debug.Log($"Log level config does not exist, using default");
+                    return null; 
+                }
+                catch (Exception exception)
+                {
+                    Debug.LogWarning($"{exception}");
+                    Debug.Log($"Exception when reading log level config, using default");
+                    return null;
+                }
 
                 List<LogLevel> logLevels = new List<LogLevel>();
                 for (int i = 0; i < LogCategoryStringArray.Length - 1; i++)