Delivery format: Support the format field on the subscription delivery spec for IMC

[Cali0707]

Problem
To allow for specifying the cloudevent format when delivering events from a subscription to an imc, we should support the format field on the delivery spec of the subscription. Specifically we will need to:

1. Add the field to the CRD
2. Depending on the value of the field, correctly configure the kncloudevents dispatcher in the imc dispatcher component to send the cloudevent with the correct binding

Persona:
Which persona is this feature for?

Exit Criteria
An e2e test indicating that subscriptions deliver events with the correct format (structured, binary, input)

Time Estimate (optional):
How many developer-days do you think this may take to resolve? 1-2

Additional context (optional)
Add any other context about the feature request here.

• Parent issue: Delivery Format: support specifying the event format #8057

[Cali0707]

/help
Note that this needs #8073 #8074 and #8076 to be resolved before it can be worked on

[knative-prow]

@Cali0707:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help
Note that this needs #8073 #8074 and #8076 to be resolved before it can be worked on

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[EraKin575]

/assign

[Cali0707]

Hey @EraKin575 just a heads up, this issue isn't ready to be worked on (as I specified in #8078 (comment) there are a few other issues which will need to be resolved first)

[EraKin575]

Sure. Thanks for informing.Please comment when it is ready to be worked on.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.