Release v19.37.2

Applications that share one event store no longer retire each other's projections when they register.

Changed

• RegisterRequest has a new optional Registrant field. Existing clients keep working; they simply no longer trigger retirement until updated.

Fixed

• Several applications registering into the same event store each sent a "full set" that retired every client-owned projection not in its own set, including the other applications'. They retired and re-registered each other's projections in a loop, which saturated the projections manager and made Register time out. A full set now only retires projections the same application registered; the client identifies itself with its entry assembly name, and a full set from a client that does not identify itself retires nothing.