Make SystemSet marker traits mutually exclusive

[joseph-gio]

Objective

Fix an issue discussed in #7882. The problem comes down to the fact that BaseSystemSet and FreeSystemSet can both be implemented for the same type, which opens the door for misuse and results in actively harmful error messages.

Solution

Use an associated type to determine whether a system set is base or not. Add blanket implementations to the marker traits based on the value of the associated type. Users are disallowed from manually implementing either marker trait due to blanket implementations, which ensures that the two traits are disjoint.

---

Migration Guide

The marker traits BaseSystemSet and FreeSystemSet can no longer be implemented manually. Instead, implement KindedSystemSet:

use bevy_ecs::schedule;

// Before:
impl schedule::BaseSystemSet for MySet {}

// After:
impl schedule::KindedSystemSet for MySet {
    // This will automatically implement `BaseSystemSet` for `MySet` due to a blanket implementation.
    type Kind = schedule::BaseSystemSetMarker;
}

[james7132]

Not confident we'll need this if base system sets are removed in #8079.

[james7132]

These traits should also be sealed to avoid users manually implementing them.