🤖 Resolve KeyError and ValueError in stack trace rule configuration

[seer-by-sentry]

👋 Hi there! This PR was automatically generated 🤖

Triggered by vu.luong@sentry.io A- a-

Fixes SENTRY-35JK

The issue arises due to a KeyError when attempting to access a 'type' key in the MATCHERS dictionary, which leads to a ValueError indicating an invalid stack trace rule configuration. The root cause is the mismatch between the key used in the stack trace rule configuration and the keys defined in the MATCHERS dictionary. To resolve this, we need to ensure that the 'type' key is correctly mapped in the MATCHERS dictionary and that the ExceptionTypeMatch class is properly defined and utilized.

The steps that were performed:

1. Update MATCHERS dictionary to include 'type' key
2. Ensure ExceptionTypeMatch class is correctly defined
3. Update FrameMatch._from_key method to include 'type' key mapping

📣 Instructions for the reviewer which is you, yes you:

• If these changes were incorrect, please close this PR and comment explaining why.
• If these changes were incomplete, please continue working on this PR then merge it.
• If you are feeling confident in my changes, please merge this PR.

This will greatly help us improve the autofix system. Thank you! 🙏

If there are any questions, please reach out to the AI/ML Team on #proj-autofix

🤓 Stats for the nerds:

Prompt tokens: 96009
Completion tokens: 2837
Total tokens: 98846

[getsantry]

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀