Comment 17 for bug 2037120

To summaries the discussion outcome:

- the secret owner will be treated just like any other consumer - we will remove the read what you just wrote behaviour
- all peer units of an application will individually track their own secret revision
- the guidance is that a new secret revision is created in a particular hook; the new secret revision is not used to update the workload until the secret changed hook arrives
- in the secret changed hook, the usual peek and refresh semantics apply