fix: resolve conventional commit validation issue and skip label requirement for forked PRs

[anket-cd]

Description

Type of Change

• 🐛 Bug fix
• ✨ New workflow
• 📝 Documentation update
• 🔧 Workflow enhancement
• 🎨 Code style/formatting
• ♻️ Refactoring
• ⚡ Performance improvement
• 🔒 Security improvement

Workflow Category

• Terraform (tf-*)
• CloudFormation (cf-*)
• Docker (docker-*)
• Helm (helm-*)
• PR Automation (pr-*)
• Security (security-*)
• Release (release-*)
• Notification (notify-*)
• AWS-specific (aws-*)
• GCP-specific (gcp-*)
• YAML Lint (yl-*)
• Other

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings
• 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
• Any dependent changes have been merged and published

Testing

I tested this on my personal GitHub account for both success and failure cases.
Or slightly better for a PR description:

Screenshots/Documentation

• Success

• Failed

Additional Notes

Functionalities Added in Your PR Validation Workflow

• Run the label check only for internal PRs, not forks.
  What happens now

PR Type	Label Validation
Internal PR	✅ checked
Fork PR	⏭ skipped

But commit + PR title validation will still run.
Example flow

Internal contributor
PR → validation runs:

PR title      ✔
commits       ✔
labels        ✔

Fork contributor
PR → validation runs:

PR title      ✔
commits       ✔
labels        ⏭ skipped

[pendharevaibhav-cd]

LGTM!