feat: add standard OSS collaboration files and GitHub templates

[Copilot]

Description

Adds standard open source collaboration infrastructure to align with OSS norms and improve contributor onboarding.

Goal

Establish standardized contribution workflow with proper templates and documentation for external contributors.

Key Changes

• CONTRIBUTING.md: Bilingual (EN/ES) guide covering setup, workflow, testing, and quality standards. Derived from COLLABORATION.md while maintaining existing file intact.
• CODE_OF_CONDUCT.md: Contributor Covenant 2.1
• SECURITY.md: Vulnerability disclosure process with response SLAs and contact methods
• GitHub Templates: YAML issue forms (bug_report.yml, feature_request.yml) and PR template with structured sections
• README.md: Enhanced Contributing section linking to all collaboration docs

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Style/UI changes
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvement
• ✅ Test updates
• 🔧 Build/configuration changes

Impact Assessment

Database Impact

• No database changes
• New migration(s) included
• Existing data migration required

Backup Impact

• No impact on backups
• Backup format changed
• Restore compatibility maintained

Testing

How Has This Been Tested?

• Unit tests
• Integration tests
• Manual testing
• Tested with SonarQube analysis

Test Steps

1. Verify all files exist at repository root and .github/ directories
2. Validate YAML syntax in issue templates
3. Confirm README links resolve to created files
4. Check COLLABORATION.md remains unmodified

Test Configuration

• Node version: N/A (documentation only)
• npm version: N/A (documentation only)
• Platform tested: Linux

UI Changes

N/A - Documentation and configuration files only.

Before

Basic Contributing section in README with minimal guidance.

After

Comprehensive collaboration documentation with structured templates for issues and PRs.

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have run npm run lint and fixed any issues
• I have run npm test and all tests pass
• I have run npm run test:electron and all tests pass
• I have run npm run sonar:check and the analysis passes
• Any dependent changes have been merged and published

Breaking Changes

• This PR contains breaking changes

Additional Context

All files maintain consistent formatting and bilingual structure where appropriate (matching COLLABORATION.md). Issue templates use YAML format for GitHub's native form rendering. COLLABORATION.md preserved per requirements - README now points to CONTRIBUTING.md as primary contributor resource.

Reviewer Notes

Verify template rendering in GitHub UI (issue/PR forms) and cross-reference links between documents.

Original prompt

Update collaboration standards for the OpenTimeTracker repo on the develop branch to align with open source norms. Add standard files and templates, and update README to reference them.

Required changes:

• Create CONTRIBUTING.md (can be derived from existing COLLABORATION.md; keep bilingual structure if appropriate) and ensure it is linked from README.
• Add CODE_OF_CONDUCT.md (use a standard OSS code of conduct such as Contributor Covenant).
• Add SECURITY.md with responsible disclosure guidance (how to report vulnerabilities, what info to include, expected response, and a security contact).
• Add GitHub issue templates under .github/ISSUE_TEMPLATE (at minimum: bug_report.yml and feature_request.yml) and a pull_request_template.md under .github/.
• Update README.md (develop) Contributing section to reference CONTRIBUTING.md and any other relevant collaboration docs (e.g., CODE_OF_CONDUCT.md, SECURITY.md).

Constraints:

• Keep COLLABORATION.md intact (do not remove) but ensure README points to the standard CONTRIBUTING.md.
• Ensure any new files follow consistent formatting and are clear for contributors.
• Do not modify unrelated application code.

Repository: altaskur/OpenTimeTracker (base branch develop).

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.