feat: implement sendComponentsV2Message for enhanced message handling with attachments

.github/copilot-instructions.md

@@ -0,0 +1,31 @@
+# Custom instructions for GitHub Copilot
+
+Whenever generating code, commit messages, or explanations related to Discord.js or the Discord API:
+
+1. Always **consult and reference** the following sources for accurate and up-to-date information:
+    - [Discord.js Guide](https://discordjs.guide)
+    - [discord.js GitHub Repository](https://github.com/discordjs/discord.js)
+    - [Discord API Types GitHub Repository](https://github.com/discordjs/discord-api-types)
+    - [Discord Developer Documentation](https://discord.com/developers/docs/intro)
+
+2. Always **prefer official documentation** over blogs, forums, or tutorials.
+    - If no clear answer is found in docs, **inspect the installed dependency in `node_modules`** to confirm if a method, property, or class truly exists.
+
+3. When suggesting code, ensure it matches the **latest stable release of Discord.js and related packages (June 2025 or newer)**.
+    - If examples belong to an older version, adapt them to the most recent stable release.
+    - If uncertain, indicate that verification against the `node_modules` implementation is required.
+
+4. When installing or suggesting npm packages related to Discord.js:
+    - Verify against their **GitHub repository** for recent updates, breaking changes, or migration notes.
+    - Always check if the changelog or releases page contains updates after **June 2025** and adjust suggestions accordingly.
+
+5. Always provide **links to relevant official documentation** (Discord.js Guide, GitHub repos, or Discord Developer Docs).
+    - If the info is missing in docs, but exists in the actual installed package, explain that and provide the discovered usage.
+
+6. **Error validation requirement:**
+    - After generating or modifying code, always remind the user to check for TypeScript errors by running:
+      ```bash
+      npx tsc --noEmit
+      ```
+      (or equivalent `tsc` command).
+    - If type errors are found, propose fixes before finalizing the solution.

.github/prompts/discord-api-expert.prompt.md

@@ -0,0 +1,15 @@
+# Prompt: Discord.js + Discord API Expert Mode
+
+Whenever assisting with Discord.js or the Discord API:
+
+- Always prioritize information from:
+    - https://discordjs.guide
+    - https://github.com/discordjs/discord.js
+    - https://github.com/discordjs/discord-api-types
+    - https://discord.com/developers/docs/intro
+- If documentation is incomplete, check the installed dependency in `node_modules`.
+- Assume **June 2025 or later** as the baseline for accuracy:
+    - Do not suggest outdated methods, deprecated classes, or old APIs.
+    - Always check whether new features or breaking changes have been introduced after this date.
+- If uncertain, clearly state that and recommend verifying with the official docs or GitHub repo.
+- Always include direct links to relevant official documentation sections.

.github/prompts/discord-helper.prompt.md

@@ -0,0 +1,14 @@
+# Prompt: Discord.js Expert Mode (Post-June 2025)
+
+Whenever assisting with Discord.js or related dependencies:
+
+- Always check official resources:
+    - https://discordjs.guide
+    - https://github.com/discordjs/discord.js
+    - https://github.com/discordjs/discord-api-types
+- If documentation is unclear or outdated, inspect the installed package in `node_modules` to verify the actual available methods and classes.
+- Treat **June 2025** as the minimum reference point:
+    - Never suggest code, methods, or patterns deprecated before June 2025.
+    - Always verify if there are new APIs, breaking changes, or version updates after this date.
+- Prefer official sources and repositories over blogs, tutorials, or old answers.
+- Always mention if information may be outdated and link to the package’s GitHub or changelog for verification.

.github/prompts/ts-validation.prompt.md

@@ -0,0 +1,7 @@
+# Prompt: TypeScript Validation Mode
+
+Whenever Copilot generates or modifies TypeScript code:
+
+- Immediately remind the user to validate changes by running:
+  ```bash
+  npx tsc --noEmit