Proto: Add ticket receipt to originated->sc-rollup

Context

Closes #4272 (closed)

Manually testing the MR

Suppose:

• Contract KT1FJaEdUJT2cMkGB8bEWAw851eQ65JArW5e mints a ticket with the content "Ticket" and sends it to the address in the parameter.
• scr1Yzn3xLdYhmgHUKU4NwBLfyQJVnBYuww6P is an address of a smart-contract rollup with ticket string as parameter.

Then running:

./octez-client transfer 0 from bootstrap1 to KT1FJaEdUJT2cMkGB8bEWAw851eQ65JArW5e --burn-cap 1 --arg 'Pair "scr1Yzn3xLdYhmgHUKU4NwBLfyQJVnBYuww6P" 1'

should result in a receipt that looks like:

  Manager signed operations:
    From: tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx
    Fee to the baker: ꜩ0.000714
    Expected counter: 3
    Gas limit: 4145
    Storage limit: 86 bytes
    Balance updates:
      tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx ... -ꜩ0.000714
      payload fees(the block proposer) ....... +ꜩ0.000714
    Transaction:
      Amount: ꜩ0
      From: tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx
      To: KT1FJaEdUJT2cMkGB8bEWAw851eQ65JArW5e
      Parameter: (Pair "scr1Yzn3xLdYhmgHUKU4NwBLfyQJVnBYuww6P" 1)
      This transaction was successfully applied
      Updated storage: Unit
      Storage size: 158 bytes
      Paid storage size diff: 66 bytes
      Consumed gas: 3038.843
      Balance updates:
        tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx ... -ꜩ0.0165
        storage fees ........................... +ꜩ0.0165
      Internal operations:
        Internal Transaction:
          Amount: ꜩ0
          From: KT1FJaEdUJT2cMkGB8bEWAw851eQ65JArW5e
          To: scr1Yzn3xLdYhmgHUKU4NwBLfyQJVnBYuww6P
          Parameter: (Pair 0x0149b8c47119e9b4fa9f9e07064a8f0447b9c302a200 (Pair "Ticket" 1))
          This transaction was successfully applied
          Consumed gas: 1005.247
          Ticket updates:
            Ticketer: KT1FJaEdUJT2cMkGB8bEWAw851eQ65JArW5e
            Content type: string
            Content: "Ticket"
            Account updates:
              scr1Yzn3xLdYhmgHUKU4NwBLfyQJVnBYuww6P ... +1
          Resulting inbox state: { level = 4
                                   current messages hash  = hash: scib21zSfCRMmi9oTReV2868nqKNwF8NutEnYG3vcQtZRNNtcNyEiAp
                                   level: 4
                                   nb_messages_in_commitment_period = 12
                                   old_levels_messages = 
       content = hash: scib22HEaHo1TetPHqBY14zMMhSVtDfdyypheuVePPrEwR89333zTWK
                                   level: 3
       index = 3
       back_pointers = scib11Yf685N5U9XAZttLgPZx3Vu3es8zrMKgpvTBhGkCZFSa5fN1yL
                                   scib134H6P9j4oE9ADFyTByEznQ2Exi9ZbcmjRgLTVwUVxKrZnLPtq1
    
                                   }

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR