.Net: Process Framework: Simplify Event Emission in Process Steps

[joslat]

Motivation and Context

Fixes: #9510

Process Framework: Simplify Event Emission in Process Steps
I would like to propose a simplification of the event emission mechanism within the Process Framework, specifically in process steps. Currently, emitting events involves multiple method calls and boilerplate code, which can make the codebase harder to read and maintain.

Description

I created an overload of EmitEventAsync with simplified signature to reduce developer cognitive load, updated some tests to verify on build.

If decided to update the signature completely (replace it) I can update all the examples and tests.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[esttenorio]

@joslat Not blocking - since this is an additional way of emitting events perhaps some of the steps in the Getting Started With Processes should have this so people are aware there are multiple ways of achieving this.

It is more likely for a person trying out Processes for the first time to check out the Getting Started samples than to check the integration tests for examples of usage

[crickman]

Not blocking - since this is an additional way of emitting events perhaps some of the steps in the Getting Started With Processes should have this so people are aware there are multiple ways of achieving this.

It is more likely for a person trying out Processes for the first time to check out the Getting Started samples than to check the integration tests for examples of usage

Step01 would be an easy update.

[joslat]

@joslat Not blocking - since this is an additional way of emitting events perhaps some of the steps in the Getting Started With Processes should have this so people are aware there are multiple ways of achieving this.

It is more likely for a person trying out Processes for the first time to check out the Getting Started samples than to check the integration tests for examples of usage

Hi @esttenorio I was thinking of providing a super-simple example with 3-4 super simple steps like this one here: https://github.com/joslat/semantic-kernel/tree/joslat-process-framework-graph-edges/dotnet/samples/ProcessDemoGraphNodesEdges for example :)