feat(bug-prediction): Allow exception type string format to be flexible

[JerrySentry]

Make the input to query to get issues by exception type to be case insensitive and ignore non alphanumeric characters.

For example when querying "ReactErrorBoundaryError" previously would not match the issues with "React Error Boundary Error" as the type in the DB

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #99617      +/-   ##
==========================================
+ Coverage   79.34%   81.25%   +1.91%     
==========================================
  Files        8595     8600       +5     
  Lines      380806   380955     +149     
  Branches    24129    24129              
==========================================
+ Hits       302151   309555    +7404     
+ Misses      78293    71038    -7255     
  Partials      362      362              

[kddubey]

ty for extensive tests. they are written a little repetitively tho. can separate out a helper, or maybe use pytest.mark.parametrize

[sentry-io]

Issues attributed to commits in this pull request

This pull request was merged and Sentry observed the following issues:

• ‼️ ThreadLeakAssertionError: <Thread(Thread-11 (run),... in fork

_{Did you find this useful? React with a 👍 or 👎}