fix(amazonq): avoid workspace context server missing historical dependency events

[LiGaCu]

Problem

There are two issues with workspace context server receiving didChangeDependencyPaths events:

• Lost initial events: Before the workspace context server properly determines user eligibility (isUserEligibleForWorkspaceContext()) and completes initialization, all didChangeDependencyPaths events sent from the IDE extension are lost.
• Lost historical events: When dependencyDiscoverer is disposed (due to user opt-out, admin opt-out or user logout), all previously received didChangeDependencyPaths events are lost as dependency maps are reset. These events cannot be recovered if the workspace context server needs to run for the user again later.

Solution

Implement an in-memory recording system for all didChangeDependencyPaths events that:

• Stores events regardless of workspace context server initialization status
• Ingests these recorded events when building initial dependency maps
• Only processes events according to the user's current qualification status

Testing

Tested the changes locally with JetBrains Amazon Q extension and verified we are no longer missing didChangeDependencyPaths events sent at the start of IDE. Also verified the original dependency discovery and upload logic is not disturbed by this change.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 37.77778% with 84 lines in your changes missing coverage. Please review.

Project coverage is 61.04%. Comparing base (788920b) to head (84eed26).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...orkspaceContext/dependency/dependencyDiscoverer.ts	2.43%	40 Missing ⚠️
...-server/workspaceContext/workspaceContextServer.ts	7.14%	13 Missing ⚠️
...endency/dependencyHandler/JSTSDependencyHandler.ts	0.00%	9 Missing ⚠️
...ncy/dependencyHandler/LanguageDependencyHandler.ts	0.00%	8 Missing ⚠️
...endency/dependencyHandler/JavaDependencyHandler.ts	0.00%	7 Missing ⚠️
...dency/dependencyHandler/PythonDependencyHandler.ts	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1946      +/-   ##
==========================================
+ Coverage   60.93%   61.04%   +0.10%     
==========================================
  Files         238      238              
  Lines       51452    51544      +92     
  Branches     3067     3067              
==========================================
+ Hits        31352    31464     +112     
+ Misses      20046    20026      -20     
  Partials       54       54              

Flag	Coverage Δ
unittests	61.04% <37.77%> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[leigaol]

this is marking workspaceFolder.uri as ingested even if some of the dependencies are failed or thrown errors, is this intentional?

[LiGaCu]

yes, this is intentional. When a folder is marked as ingested, the future didChangeDependencyPaths events from IDE would trigger dependency map update again.