Split the `Window` component for more granular change detection

[alice-i-cecile]

A more sophisticated version could split the Window struct into multiple components that are connected as relationships. That way, we can have working change detection for all of them. But I'd prefer to get this fix merged first and leave a Window redesign for a dedicated PR :)

Originally posted by @janhohenheim in #19629 (comment)

[janhohenheim]

Update per discussion on Discord:
We settled on using required components and the following new API:
Old:

App::new()
    .add_plugins((
        DefaultPlugins.set(WindowPlugin {
            primary_window: Some(Window {
                present_mode: PresentMode::AutoNoVsync,
                ..default()
            }),
            cursor_options: Some(CursorOptions {
                visible: false,
                ..default()
            }),
            ..default()
        }),
    ))

New:

App::new()
    .add_plugins(DefaultPlugins)
    .add_observer(configure_window)

fn configure_window(trigger: On<Add, PrimaryWindow>, mut commands: Commands) {
    commands.entity(trigger.target()).insert((
        Window {
            present_mode: PresentMode::AutoNoVsync,
            ..default()
        },
        CursorOptions {
            visible: false,
            ..default()
        }),
    ));
}

[janhohenheim]

Putting this in the milestone because otherwise, the CursorOptions being separated feels lonely