chore: add "breaking change" prefixes to allowed prefix list.

[Felix Frank (feliopterix)]

1. Why is this change necessary?

No breaking change prefix are allowed by our semantic PR action.

2. What does this change do, exactly?

Adds breaking change prefixes to the allowed type list.

3. Describe each step to reproduce the issue or behaviour.

4. Please link to the relevant issues (if any).

5. Checklist

• I have rebased my changes to remove merge conflicts
• I have written tests and verified that they fail without my change
• I have written or adjusted the documentation according to my changes
• This change has comments for package types, values, functions, and non-obvious lines of code
• I have read the contribution requirements and fulfil them.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.67%. Comparing base (d33e39c) to head (298c87b).
⚠️ Report is 19 commits behind head on trunk.

Additional details and impacted files

@@            Coverage Diff             @@
##            trunk     #229      +/-   ##
==========================================
- Coverage   99.69%   99.67%   -0.02%     
==========================================
  Files         141      146       +5     
  Lines        7435     7802     +367     
  Branches     1723     1809      +86     
==========================================
+ Hits         7412     7777     +365     
- Misses         23       25       +2     

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

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.