We actually already have methods like this, as `+[RACSignal startLazilyWithScheduler:block:]` and `+startEagerlyWithScheduler:block:`, but having those as signal methods has always felt a bit weird to me.

This puts them in the correct place, IMO, and moves the decision about eager/lazy evaluation to the consumer rather than the producer.