gh-141984: Add "exhausted" to glossary, link existing mentions

[encukou]

The term “exhausted” is used quite a lot for iterators. Add a glossary entry for it, and link to that from all relevant uses. (Things like memory exhaustion or non-exhaustive lists aren't linked.)

(Tagged with #141984 since this grew out of improving syntax docs. It's only tangentially related, but IMO better than not linking to an issue.)

• Issue: Reword the Expressions chapter of the docs #141984

[read-the-docs-community]

Documentation build overview

📚 cpython-previews | 🛠️ Build #34474629 | 📁 Comparing 01c089c against main (52ffffe)

  🔍 Preview build  

10 files changed · ± 10 modified

± Modified

• glossary.html
• c-api/typeobj.html
• howto/functional.html
• library/collections.html
• library/functions.html
• library/http.client.html
• library/itertools.html
• library/unittest.mock.html
• reference/compound_stmts.html
• tutorial/controlflow.html

[StanFromIreland]

Suggested change

	:py:func:`next`) raise :py:exc:`StopIteration`
	(or :py:exc:`StopAsyncIteration` in the case of an :term:`asynchronous
	:func:`next`) raise :exc:`StopIteration`
	(or :exc:`StopAsyncIteration` in the case of an :term:`asynchronous

Why are we specifying the :py: domain here, it's the default?

[encukou]

I work on pure-Python & C API docs, so I tend to write the domain explicitly rather than look at the current file's default. I hope that's not a problem.

[StanFromIreland]

I'd personally prefer not to add domains when we don't have to (i.e., outside of the C-API docs). I find the extra qualification just adds noise to the docs, and admittedly, I also prefer to be consistent.

But, I won't block on this.