gh-150207: type-crash(): make helpers.c in tokenizer throw a no mem error

[grantlouisherman]

Original report was around this snippet of code:
import resource MB_512 = 512 * 1024 * 1024 resource.setrlimit(resource.RLIMIT_AS, (MB_512, MB_512)) eval("A"* 420000000)

Throwing a system error. Based off the write up made in #150207 I felt like there was a fair case to actually show the user a Mem error instead of a system crash.
`>>> import resource
... MB_512 = 512 * 1024 * 1024
... resource.setrlimit(resource.RLIMIT_AS, (MB_512, MB_512))
... eval("A"* 420000000)
...
Traceback (most recent call last):
File "", line 4, in
eval("A"* 420000000)
~~~~^^^^^^^^^^^^^^^^
MemoryError

`

I think this does provide a bit nicer of an experience but I think I need an actual adult to verify this for me. I also dont know the larger ramifications but it felt worth to throw something up

• Issue: Allocation failures generated in _PyTokenizer_FromUTF8 lead to SystemError/abort()s #150207

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.