fix(toolkit): initialize compute region in get call with a default value to fix extension activation failure

[parameja1]

Problem

With updating Toolkit version to latest in SMUS CodeEditor Spaces, observing Toolkit throws an error as attached in screenshot below with error message

Attempted to get compute region without initializing

Solution

• Get Compute Region seems to be invoked first before Initializing compute region is called

• hence solution is to start the async operation of initialize compute region in the background and set a default value, immediately to prevent future calls from throwing error in order to not fail the toolkit extension activation

• Tested with a local debug artifact in SMUS CodeEditor space, toolkit activation completed and working

• 

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.

• Your code changes must meet the guidelines in CONTRIBUTING.md.

• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[justinmk3]

By removing this, you are hiding a problem.

The error exists to ensure that order-of-operations is correct. After your change, that guarantee will no longer be possible.

It seems convenient now, but is a short-term solution with long-term consequences.

[parameja1]

Thanks for the question, though the Error is removed in terms of order-of-operations the above implementation ensures initializeComputeRegion is being called within getComputeRegion to handle case where user may not set it correctly. Also default region being set follows same logic from initializeComputeRegion

• curious why not handle initialize region within get call above?

[parameja1]

CR closed to address the issue with a different approach as suggested in the comments