Expose annotation to anonymous virtual memory ranges to mmap module

[corona10]

Feature or enhancement

Proposal:

Since the annotation of anonymous virtual memory ranges has landed
(c4ccaf4),
We can now consider exposing this feature to end users as well.

#141770 (comment)

@encukou proposed adding a name parameter to mmap.mmap, and I think this would be a great addition.
It would make debugging much easier by allowing people to identify and track individual mmap allocations.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

#141770 (comment)

[corona10]

cc @vstinner

[SpecLad]

Since the underlying system call annotates an existing memory range, wouldn't it more natural for this to be a method call on the mmap object? E.g. mm = mmap.mmap(...); mm.set_name("foobar"). That way you could also change the name multiple times.