Update function signatures to use `*` and `/` as needed

Documentation

[!CAUTION]
For new contributors, please do not consider this issue as an "easy" one. While the changes may seem mechanical, they are not necessarily trivial as this requires to know what really happens (both at a Python and a C level).

This is tracks cases where changes need to be made to enact the Editorial Board's decision for function signature markup.

• builtins:
  • min()
  • max()
  • range()
  • map()
• methods on builtins:
  • dict.get(), dict.setdefault()

See also:

• https://discuss.python.org/t/editorial-board-decisions/58580
• https://github.com/python/cpython/pull/129669#issuecomment-2636839784
• https://discuss.python.org/t/81003
• https://devguide.python.org/documentation/style-guide/#function-signatures
• https://discuss.python.org/t/58750

Linked PRs

• gh-131868
• gh-131886
• gh-128208
• gh-131893
• gh-131894
• gh-131990
• gh-131992
• gh-132029
• gh-136085
• gh-136120
• gh-136121
• gh-137656
• gh-137657
• gh-137902
• gh-137904
• gh-139978
• gh-140270
• gh-144856
• gh-156179
• gh-156267
• gh-156268
• gh-156269

從剩餘的未勾選 map() 項目開始，檢視函式簽章指南以及 Editorial Board 的相關討論。檢查相關的內建文件和現有的關聯 PRs；當適用的簽章依照約定的標記一致地使用 * 和 / 時，工作即完成。