[ci] Add automated PR title check(#13867)

[aHenryJard]

Proposed changes

• Add a very permissive regexpr to check PR title:
  • start with [anyword]
  • ends with (# anyNumber)

OR

• starts with[deps] (for renovate PRs)

Related issues

• closes Automatically check PR title with contributing.md format #13867

Example of failure.

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case (coverage and e2e)
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality

Further comments

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 32.36%. Comparing base (1fb52ee) to head (351335d).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #13868    +/-   ##
========================================
  Coverage   32.36%   32.36%            
========================================
  Files        3096     3096            
  Lines      210896   210896            
  Branches    38196    38483   +287     
========================================
  Hits        68259    68259            
  Misses     142637   142637            

Flag	Coverage Δ
opencti-client-python	45.50% <ø> (ø)
opencti-front	2.83% <ø> (ø)
opencti-graphql	67.73% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR adds automated validation of pull request titles using a GitHub Actions workflow. The workflow enforces that PR titles follow the format [component] Message (#issuenumber) as specified in the CONTRIBUTING.md file.

Changes:

• Adds a new GitHub Actions workflow that triggers on PR open/edit events
• Uses the Slashgear/action-check-pr-title action to validate PR title format
• Provides a help message pointing to contribution guidelines

[aHenryJard]

@copilot change the regexpr in this pull request to allow title format with "[backend/frontend] blabla (#1234)" or "[docs] blabla (#1234)(#4567)"

[Copilot]

@aHenryJard I've opened a new pull request, #14605, to work on those changes. Once the pull request is ready, I'll request review from you.

[fellowseb]

This works as a permissive solution (:. (the presence of .*s basically opens the door to many wild stuff, be we can refine later if we want to !)
Just for the component part consider either removing the [a-z]+ part given the .+ already allows anything, or constraining it more (like [\[[a-z\/\-]+\])