Agent skill + Dio migration + Rebase

[HumbleBee14]

This pull request introduces several improvements and refactorings to the Roopik Dio extension, focusing on a major rebranding of the extension, enhancements to the custom tool registry and build process, and improved test coverage. The most significant changes are grouped below.

Rebranding and Naming Updates:

• Updated the extension's name, display name, author, and various references from "Roo Dio" and "Roopik" to "Dio" across package.json, package.nls.json, and related metadata and UI strings. This includes commands, categories, configuration titles, and quick fix labels. [1] [2] [3] [4] [5] [6] [7] [8]

Custom Tool Registry and Build System Improvements:

• Enhanced the custom tool registry to use tool-specific subdirectories for caching compiled TypeScript files, preventing .env file conflicts between tools and ensuring proper isolation. The cache clearing logic now removes entire subdirectories, not just flat files. [1] [2]
• Updated the dynamic import logic to bundle TypeScript tools with esbuild, keeping Node.js built-in modules external, bundling npm packages with a CommonJS shim, and copying .env files to the tool-specific cache directory. [1] [2]

Build and Source Control Hygiene:

• Added .gitignore rules to prevent committing compiled JavaScript files and dist directories in all subpackages, improving repository cleanliness and avoiding accidental check-ins of build artifacts. [1] [2] [3]

Esbuild Runner Enhancements:

• Introduced NODE_BUILTIN_MODULES (using Node's built-in module list) and COMMONJS_REQUIRE_BANNER (for ESM/CommonJS compatibility) in the esbuild runner, and extended EsbuildOptions to support external modules and custom banner code. The esbuild CLI invocation now respects these options. [1] [2] [3]

Test Coverage Improvements:

• Expanded tests for the esbuild runner to verify correct handling of external modules, custom banners, the CommonJS require shim, and the built-in modules list. [1] [2]

These changes collectively improve the extension's branding, reliability, testability, and maintainability.<!-- Thank you for submitting a Pull Request. Please:

• Read our Pull Request guidelines:
  https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests
• Associate an issue with the Pull Request.
• Ensure that the code is up-to-date with the main branch.
• Include a description of the proposed changes and how to test them.
  -->