[debug-certificate-mangaer] remove shell integration timeout and make make activation event more specific

[bmiddha]

Summary

Remove timeout for VS Code shell integration
Make activation event more specific

Details

We had reports where users of the Debug Certificate Manger VS Code extension kept running into shell integration timeouts. This can happen when the shell boot up.
Shell integration is activated after the config files are sourced. So if there is anything in the .bashrc or .bash_profile that takes a while then the bash shell integration will be delayed.

We also had cases where the extension does not activate even when .vscode/debug-certificate-manager.json
Extension host logs:

2025-08-26 13:51:17.935 [info] Not activating extension 'ms-RushStack.debug-certificate-manager': Timed out while searching for 'workspaceContains' pattern .vscode/debug-certificate-manager.json

Updated activation event to be more specific in the file pattern. Hopefully this will make the search faster and not timeout.

How it was tested

Tested by adding sleep 10 to .bashrc

Tested that the extension still activates with the new pattern

2025-08-26 14:35:12.672 [info] ExtensionService#_doActivateExtension ms-RushStack.debug-certificate-manager, startup: true, activationEvent: 'workspaceContains:/.vscode/debug-certificate-manager.json'