Consider populating realAddress and userAddress for scheduled data

[SebastienGllmt]

Right now both realAddress and userAddress are set to 0x0 for scheduled data.

However, you may want to know which user transaction triggered the primitive. There are essentially 3 addresses you care about:

1. The address of the contract that emitted the event (can get this from getDynamicExtensionByName. Not sure why this utility function is specific to dynamic primitives though)
2. The address that created the transaction
3. The address that called the smart contract (note: in EVM these can be different due to internal transactions. In Cardano, these are always the game)

However, it's not clear we should actually do anything about this because:

1. Things work differently depending on the chain, which makes this a bit tricky to decide what is the most logical way to handle this
2. It's not strictly required since you can just include whatever address you care about inside the event you emit

It's something we can think about though if a compelling use-case comes up