Change Application.isEditor check order in InitializeSingularSDK in editor

[VsIG-official]

Description

1. Awake and InitializeSingularSDK initialization flow order in editor

While initializing SingularSDK via InitializeSingularSDK in the Unity Editor I've encountered error SingularSDK InitializeSingularSDK, no instance available - cannot initialize.

It seems like strange behavior to Me because this error occurs when there's no SingularSDK instance, however, it's impossible for the instance to exist because there's a check in Awake before its creation to ensure, if We are in the editor, then return.

So in My PR I've changed Awake to be more like InitializeSingularSDK: firstly check if We're in the editor and then - if We have an instance of SingularSDK

Before fix:

• Awake - if(Application.isEditor) -> if(instance)
• InitializeSingularSDK - if(!instance) -> if(Application.isEditor)

After fix:

• Awake - if(Application.isEditor) -> if(instance)
• InitializeSingularSDK - if(Application.isEditor) -> if(!instance)

Commit

2. Private keywords, whitespaces and unused methods

Also I've added private keywords to Unity methods and deleted some whitespaces + unused Update method

Commit 'whitespaces and unused methods'

Commit 'access keywords'