feat(builder): support ProcessCommand action in Execute Script V2

[lucasmiqueias]

Context

Execute Script V2 already exposes helper functions for some Builder actions, but it still does not provide a dedicated function to execute Process Command.
This blocks script scenarios that need to trigger commands in a native, consistent way with the other available functions.

References

• https://github.com/takenet/blip-sdk-csharp/tree/master/src/Take.Blip.Builder/Actions/ExecuteScriptV2
• https://github.com/takenet/blip-sdk-csharp/tree/master/src/Take.Blip.Builder/Actions/ProcessCommand

Problem

Execute Script V2 is missing a public function, similar to existing exposed action helpers, that encapsulates and runs ProcessCommandAction.

Goal

Expose a new function in Execute Script V2 to process commands using the same conventions as other script-exposed actions and reusing ProcessCommandAction internally.

Proposed Solution

1. Add a new script-exposed function in Execute Script V2, following the same naming and signature style used by existing functions.
2. Internally build and execute ProcessCommandAction.
3. Keep validation, serialization, and exception handling aligned with current Execute Script V2 behavior.
4. Update Execute Script V2 documentation with usage examples.

Acceptance Criteria

1. A new Execute Script V2 function is available to execute Process Command.
2. The function produces the same behavior expected from ProcessCommandAction when used outside scripts.
3. Invalid command payloads fail with predictable, traceable error messages.
4. Automated tests cover success and failure scenarios.
5. Documentation is updated with at least one real example.

Minimum Test Scenarios

1. Valid command execution returns the expected result.
2. Invalid command payload fails according to current Execute Script V2 error handling patterns.
3. Execution respects script timeout and cancellation behavior.
4. Existing scripts remain compatible with no breaking changes.

Expected Impact

This enables richer automations in Execute Script V2, removes workarounds, and brings script capabilities closer to native Builder actions.

Risks and Considerations

1. Ensure the new function does not allow command execution beyond existing platform constraints.
2. Keep tracing and logs consistent for troubleshooting.
3. Validate performance impact inside the Execute Script V2 runtime.