in #350, a central default broker is used for all sinkbindings and triggers' broker is hardcoded as 'default'. therefore It is expected that user can have the flexibility to manage the config of generated knative eventing resources from Sonataflow/SonataflowPlatform CR

as suggested here. user should be able to specify different brokers for events:
`spec:
events:
sink:
... # YOUR PROPOSAL
triggers:

• event:
  broker: `

where all the options can still have a defined defaults from spec.sink

github issue: https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/355