Expand test logging during extension activation/deactivation

[plemarquand]

Description

Provide more robust logs during extension activation/deactivation in order to help track down test timeouts. These logs are only printed if a test fails to avoid cluttering up the test report.

This additional logging uncovered several test related issues:

• A background compilation task could have started after the BackgroundCompilation object was disposed
• TaskQueues were not disposed and would continue to process tasks after the parent TaskManager was disposed
• DYLD_FRAMEWORK_PATH/DYLD_LIBRARY_PATH should be set in the environment when debugging test both kinds of test executables on >=6.2
• The FolderContexts created in FolderContext.test.ts were not being disposed, causing their BackgroundCompilation to run at undesirable times
• The LanguageClientIntegration suite setup was doing a build all with test discovery enabled. Because the LSP isn't yet configured at this point, the extension would fall back to trying to discover tests with swift test --list-tests unexpectedly.
• The ProjectPanelProvider did not dispose its listeners, and was not always being disposed correctly in the tests.

Tasks

• Required tests have been written
• Documentation has been updated
• Added an entry to CHANGELOG.md if applicable

---