Make sure child instantiation service instances are disposed/tracked for disposal

[jrieken]

Since recently the instantiation service is disposable. A instantiation service will dispose all service instances it has created and will dispose all its children. In return, children should also be explicitly disposed so that they get released from their parents. This item tracks the adoption of registering child instantiation service instances with a disposable.

^* This became an issue because we now prevent GC'ing of child service and thereby implicit clean-up. So, while this is more work/tracking it is true disposing of services. Overall, this isn't severe because the vast majority of insta-children are for scoped context key services

[jrieken]

Best-guess assignment, please re-assign along the way. A sample adoption is d1fdc09

• src/vs/workbench/api/browser/mainThreadCLICommands.ts @aeschli
• src/vs/workbench/api/common/extHostExtensionService.ts
• src/vs/workbench/contrib/comments/browser/commentThreadZoneWidget.ts @alexr00
• src/vs/workbench/contrib/terminal/browser/terminalInstance.ts @Tyriar
• src/vs/workbench/services/textfile/test/browser/browserTextFileService.io.test.ts
• src/vs/workbench/services/textfile/test/electron-sandbox/nativeTextFileService.io.test.ts
• src/vs/workbench/services/textfile/test/electron-sandbox/nativeTextFileService.test.ts
• src/vs/workbench/test/browser/contributions.test.ts

[alexr00]

Took care of mine last month with #213808