refactor: remove duplicate add_comment and add_label methods from IssueTools

- Removed duplicate dd_comment method (kept dd_comment_to_issue)
- Removed duplicate dd_label method (kept dd_label_to_issue)
- Updated dispatcher.py to remove duplicate tool registrations
- Updated coding_prompt.py to reference only dd_comment_to_issue
- Removed corresponding duplicate tests from test_issue_tools.py

This addresses section 10.1 (Confusing Naming) in bad_code.md

core/coding_prompt.py

@@ -119,7 +119,7 @@ Before writing any code or making any changes, you MUST:
    - Could multiple approaches work and you're unsure which to pick?
 
 3. **If ANY uncertainty exists** — STOP and ask before implementing:
-   - Post a comment on the issue or PR (using `add_comment_to_issue` or `add_comment` tool) with your specific question(s).
+   - Post a comment on the issue or PR (using `add_comment_to_issue` tool) with your specific question(s).
    - List the approaches you are considering and ask which is preferred.
    - **Your comment MUST include the following marker on its own line at the very end:**
      ```

core/dispatcher.py

@@ -165,8 +165,6 @@ class TaskProcessor(ABC):
             self.pr_tools.close_pull_request,
             self.issue_tools.get_issue_comments,
             self.pr_tools.get_pull_request_comments,
-            self.issue_tools.add_comment,
-            self.issue_tools.add_label,
             self.file_tools.update_file,
             self.pr_tools.get_pull_request_diff,
             self.pr_tools.get_pull_request_patch,