Remove Py_C_RECURSION_LIMIT & PyThreadState.c_recursion_remaining

[encukou]

Both were added in 3.13, are undocumented, and don't make sense in 3.14 due to changes in the stack overflow detection machinery. (On current main they contain dummy values.)

SC exception for removal without deprecation: python/steering-council#288

Linked PRs

• gh-133079: Remove Py_C_RECURSION_LIMIT & PyThreadState.c_recursion_remaining #133080

[colesbury]

Looks like this will affect greenlet: https://grep.app/search?q=Py_C_RECURSION_LIMIT. Heads up to @jamadden

[markshannon]

We may still need this for webassembly builds, as they have two stacks and we need a way to protect against either overflowing.
#130397

[encukou]

Is it needed in public headers? If so, could you document it?