Language Specific Security Skills Base on Intel Secure Coding Standards

[ltalarcz]

📝 Description

This pull request introduces Intel-based secure coding guidelines for both C++ and Python, and updates the main security skill to reference these new language-specific documents. These additions provide detailed, actionable best practices and review checklists tailored for SceneScape's C++ and Python codebases, helping ensure secure development and code review processes.

New language-specific secure coding guidelines:

• Added .github/skills/intel-secure-cpp-specifics.md with secure C++ coding practices, including RAII, type safety, error handling, integer arithmetic, and a code review checklist, all based on Intel Secure Coding Standards.
• Added .github/skills/intel-secure-python-specifics.md with secure Python practices covering input validation, string handling, authentication, file/network I/O, error handling, project structure, deployment, and a review checklist, following Intel's secure coding guidance.

Security skill documentation update:

• Updated .github/skills/security.md to reference the new C++ and Python secure coding guideline documents, directing contributors and reviewers to language-specific best practices.

✨ Type of Change

Select the type of change your PR introduces:

• 🐞 Bug fix – Non-breaking change which fixes an issue
• 🚀 New feature – Non-breaking change which adds functionality
• 🔨 Refactor – Non-breaking change which refactors the code base
• 💥 Breaking change – Changes that break existing functionality
• 📚 Documentation update
• 🔒 Security update
• 🧪 Tests
• 🚂 CI

🧪 Testing Scenarios

Describe how the changes were tested and how reviewers can test them too:

• ✅ Tested manually
• 🤖 Ran automated end-to-end tests

✅ Checklist

Before submitting the PR, ensure the following:

• 🔍 PR title is clear and descriptive
• 📝 For internal contributors: If applicable, include the JIRA ticket number (e.g., ITEP-123456) in the PR title. Do not include full URLs
• 💬 I have commented my code, especially in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ✅ I have added tests that prove my fix is effective or my feature works

[saratpoluri]

We will need to set the proper hierarchy for what is auto discoverable and what will be hierarchically loaded as part of security guidelines. I will make that change across the repo later. For now, this looks good to me.