Group End and Transition properties

[cdavernas]

What would you like to be added:
Group End and Transition properties, in such way that we can address it as an (activity | state | workflow) outcome.

In other words, what I'd like to achieve is:

...
states:
  - name: MyState
    outcome:
      type: end
      produceEvents: ...
    ...
...

Why is this needed:

Because End and Transition properties are mutually exclusive, and implicitly defines the outcome of an (activity | state | workflow), it makes sense to call is as such. In addition, it simplifies processing of the whole definition, by checking that an outcome has been specified instead of having to do checks on multiple properties. @tsurdilo WDYT?

[tsurdilo]

Yes, i wish we did this to begin with. Will update

[cdavernas]

I'm working on it, PR should be ready by Monday;)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lsytj0413]

/remove-stale

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cdavernas]

Closed as resolved by 1.0.0-alpha1, and therefore as part of #843