feat: Comment out working_commits for verification (#3323)

[Sukuna0007Abhi]

Summary

This PR addresses issue #3323 by commenting out all working_commits table usage to verify it's no longer needed before permanent removal. This is PR using approach to safely remove legacy code.

Changes Made

All working_commits related code has been commented out with # TESTING: Commented out for issue #3323 markers:

1. Database Library Functions (lib.py)

• Commented out get_working_commits_by_repo_id()
• Commented out remove_working_commits_by_repo_id()
• Commented out remove_working_commits_by_repo_id_and_hashes()

2. Facade Tasks (facade_tasks.py)

• Removed working_commits imports (line 8)
• Commented out working_commits check in trim_commits_facade_task() (lines 93-97)
• Commented out cleanup call in analyze_commits_in_parallel() (line 336)

3. Analyze Commit Worker (analyzecommit.py)

• Commented out INSERT INTO working_commits statement (line 172)

4. Utility Methods (utilitymethods.py)

• Removed working_commits imports and cleanup calls from trim_commits()

Testing Performed

Created and ran validation script that confirmed:

PASS: Database tables exist (both at 0 rows)
PASS: Module imports work without errors
PASS: working_commits functions are properly disabled
PASS: commits table remains accessible

Related

• Issue Remove potentially legacy working commits call/table #3323

Fixes #3323

Pls review @sgoggins @MoralCode @cdolfi

[MoralCode]

marking as draft since this is mentioned as being a testing PR

[Sukuna0007Abhi]

I verified it in my end, that all working_commits tables are no more usable.. so I will do some more changes and make it ready for review by today...