fix: id generation for env and pkg managers

[karthiknadig]

Fixes #223

[vs-code-engineering]

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

[Copilot]

Pull Request Overview

This PR fixes an issue with environment manager ID generation by updating error messages and enhancing trace outputs for improved debugging and consistency.

• Updated error messages in environment managers to provide more context
• Added trace outputs listing available manager IDs
• Refined logic in frameUtils to better determine the calling extension ID

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/features/envManagers.ts	Updated error messages and added trace outputs for missing managers
src/common/utils/frameUtils.ts	Modified frame filtering and error handling in extension detection

Comments suppressed due to low confidence (3)

src/features/envManagers.ts:264

• [nitpick] Consider standardizing the error message format for missing environment managers so both locations follow a similar pattern for clarity.

`No environment manager found for scope: ${ customScope instanceof Uri ? customScope.fsPath : customScope?.environmentPath?.fsPath }`

src/features/envManagers.ts:302

• [nitpick] Standardize the error message format here to match the updated pattern used above, ensuring consistent logging across the module.

`No environment manager found for [${environment.envId.managerId}]: ${ environment.environmentPath ? environment.environmentPath.fsPath : '' }`

src/common/utils/frameUtils.ts:70

• [nitpick] Consider providing a more descriptive error message that indicates which extension is missing, improving debuggability.

if (!envExt || !pythonExt) { throw new Error('Something went wrong with feature registration'); }