Trigger stack runs when contexts change

We are making extensive use of contexts to both share configuration between stacks and also split configuration from code more cleanly.

A problem we have though is when configuration of a context changes this will not trigger a run of stacks it is attached to. Ideally contexts should behave like dependencies do with the ability to trigger (either implicitly or via a trigger policy) when a change to them occurs.