In memory subscribable status (fix fallout from #1330)

[vaikas]

References #1189

Proposed Changes

• Change InMemoryChannel to conform to the new subscribable status.
• Namely now have these fields:
  duckv1alpha1.AddressStatus json:",inline"
  eventingduck.SubscribableTypeStatus json:",inline"
• Modeled after Channel and Subscription Readiness #1330

Release Note

Change the Status.Addressable to inlined: duckv1alpha1.AddressStatus
Add inlined: eventingduck.SubscribableTypeStatus

[matzew]

do we need something for finalizers, like:

eventing/config/provisioners/in-memory-channel/in-memory-channel.yaml

Lines 48 to 54 in 01fcacd

	- apiGroups:
	- eventing.knative.dev
	resources:
	- channels/finalizers
	- clusterchannelprovisioners/finalizers
	verbs:
	- update

[vaikas]

My changes should not require anything about that, just that the dispatcher needs to update /status. Or mayhaps I misunderstand what you meant.

[knative-metrics-robot]

The following is the coverage report on pkg/.
Say /test pull-knative-eventing-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/reconciler/inmemorychannel/dispatcher/inmemorychannel.go	83.3%	84.1%	0.8

[matzew]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew, vaikas-google

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vaikas-google]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment