Gitty Events are propagated to NOS

As a developer, merge events are propagated from Gitty to NOS and therefore being processed.

In order to pass enough context information; we might need to rely on a specific Operation that schedule a demultiplex work.
We use Portal Auth to comunicate from Gitty to NOS

AC:

• After a merge is done on Gitty, NOS is notified with information like: Studio Project, branch, author, date , commit hash