DOC: Prepare 1.17.0rc2 release.

- Update mailmap.
- Update changelog.

[ci skip]

DEP: Speed up WarnOnWrite deprecation in buffer interface

DOC: show workaround for backward compatibility

DOC: Document array_function at a higher level.

When a buffer interface does not request a writeable buffer,
simply pass a read-only one when the warn on write flag is set.

This is to give an easier way forward with avoiding the deprecation
warnings: Simply do not ask for a writeable buffer.

It will break code that expects writeable buffers but does not
ask for them specifically a bit harder than would be nice.
But since such code probably should ask for it specifically, this
is likely fine (an RC release has to find out).

The main reason for this is, that this way it plays very will with
cython, which requests writeable buffers explicitly and if declared
`const` is happy about read-only (so that using `const` is the best
way to avoid the warning and makes code cleaner).

Closes gh-13929, gh-13974