disable upstream workflow actions not needed in kilocode repo

[markijbema]

Summary

• Disables compliance-close, duplicate-issues, pr-management, and pr-standards workflow jobs using if: false
• These workflows auto-comment, label, and close issues/PRs — behaviour we don't want in the kilocode repo
• Changes are marked with kilocode_change comments to make upstream merges easy to resolve
• stale-issues and close-stale-prs are left intact

This is just way out of hand: Kilo-Org/kilo#153 (comment)
https://discord.com/channels/1349288496988160052/1391109167275577464/1475943352984801493

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Clean, straightforward PR that disables upstream workflow actions not needed in the kilocode repo. All changes consistently use if: false with kilocode_change marker comments, following the established fork merge conventions.

Note: In duplicate-issues.yml, the recheck-compliance job (line 123) is not disabled, but it effectively becomes dead code since the check-duplicates job that would add the needs:compliance label is now disabled. This is harmless but could be disabled for completeness in a follow-up if desired.

Files Reviewed (4 files)

• .github/workflows/compliance-close.yml - Disabled close-non-compliant job
• .github/workflows/duplicate-issues.yml - Disabled check-duplicates job
• .github/workflows/pr-management.yml - Disabled check-author, check-duplicates, and add-contributor-label jobs
• .github/workflows/pr-standards.yml - Disabled check-author and check-standards jobs