Spike: can we transition the time resource to an inbound notification that triggers connected jobs when it fires? #3595
Description
Related: concourse/rfcs#10, #3585
Previously we've thought of notifications as purely outbound, but in light of the pain of 'resource scopes' (and how it will be exacerbated by 'spaces'), can we remodel the time resource as an inbound notification for triggering jobs? This way we can eliminate unique_version_history and resource scopes without any hacky business.