MaybeUninit inherent slice methods part 2

[clarfonthey]

These were moved out of #129259 since they require additional libs-api approval.

New API surface:

impl<T> [MaybeUninit<T>] {
    // replacing fill; renamed to avoid conflict
    pub fn write_filled(&mut self, value: T) -> &mut [T] where T: Clone;

    // replacing fill_with; renamed to avoid conflict
    pub fn write_with<F>(&mut self, value: F) -> &mut [T] where F: FnMut() -> T;

    // renamed to remove "fill" terminology, since this is closer to the write_*_of_slice methods
    pub fn write_iter<I>(&mut self, iter: I) -> (&mut [T], &mut Self) where I: Iterator<Item = T>;
}

Relevant motivation for these methods; see #129259 for earlier methods' motiviations.

• I chose write_filled since filled is being used as an object here, whereas it's being used as an action in fill.
• I chose write_with instead of write_filled_with since it's shorter and still matches well.
• I chose write_iter because it feels completely different from the fill methods, and still has the intent clear.

In all of the methods, it felt appropriate to ensure that they contained write to clarify that they are effectively just special ways of doing MaybeUninit::write for each element of a slice.

r? libs-api

[clarfonthey]

@rustbot blocked

[clarfonthey]

@rustbot ready