The options are a bit muddled here. I think we need to separate what to do about the sensors we have in providers from the core interface, essentially.
Reschedulability in airflow (making up a word here) to my knowledge only exists to support reschedule mode in sensors. Let's also separate poke from reschedule. For now, let's just look at reschedule. Let me enumerate some paths as i see them. 1. remove the rescheduling interface in core. No more "up for reschedule" state etc. No more reschedule mode in base sensor. No more reschedule mode in any derivative sensor. 2. keep rescheduling in core. remove from base sensor and derivatives. 3. keep reschedule in core. keep in base sensor. remove from all derivatives. ban the reintroduction of reschedule mode in derivative sensors.
