fix(smus): Fix potential race condition bug on getting context

**Description**

We were seeing intermittent issues where sometimes the context was
being returned as undefined.

Setting it at the start of the activation to ensure the the context is
available always.

**Motivation**

Bug fix

**Testing Done**

Tested manually locally.

Author: Bhargava Varadharajan

packages/core/src/sagemakerunifiedstudio/activation.ts

@@ -8,11 +8,15 @@ import { activate as activateConnectionMagicsSelector } from './connectionMagics
 import { activate as activateExplorer } from './explorer/activation'
 import { isSageMaker } from '../shared/extensionUtilities'
 import { initializeResourceMetadata } from './shared/utils/resourceMetadataUtils'
+import { setContext } from '../shared/vscode/setContext'
+import { SmusUtils } from './shared/smusUtils'
 
 export async function activate(extensionContext: vscode.ExtensionContext): Promise<void> {
     // Only run when environment is a SageMaker Unified Studio space
     if (isSageMaker('SMUS') || isSageMaker('SMUS-SPACE-REMOTE-ACCESS')) {
         await initializeResourceMetadata()
+        // Setting context before any getContext calls to avoid potential race conditions.
+        await setContext('aws.smus.inSmusSpaceEnvironment', SmusUtils.isInSmusSpaceEnvironment())
         await activateConnectionMagicsSelector(extensionContext)
     }
     await activateExplorer(extensionContext)