Remove any logic specific to Device ID

[kristinapathak]

Currently, caduceus parses the device ID in two places:

caduceus/outboundSender.go

Line 582 in 453f141

id, _ := device.ParseID(msg.Source)

caduceus/outboundSender.go

Line 391 in b2866f4

if deviceRegex.MatchString(msg.Source) {

In talking with @schmidtw, we have reason to believe some consumers are using the device ID header, and we should probably keep that accurate. The part of the webhook struct that provides regex to apply against the device ID was more intended as a way to provide regex against the wrp.Source, so perhaps we could change the api to reflect that better without changing the Caduceus logic.

In our discussion, we didn't think Caduceus should be responsible for parsing the device ID from the event. Talaria knows the device ID already, so if it passes it to Caduceus, Caduceus could forward it - either as an http header or a new field in the wrp.

These are just options we discussed; further discussion is needed.

---

Update:
Given our discussion, these are the changes needed in Caduceus:

• Remove webhook.Matcher regex logic
• Remove adding specific Device ID headers in Caduceus (wrphttp package will add any needed headers)

This is dependent on xmidt-org/wrp-go#53 and https://github.com/xmidt-org/webpa-common/issues/514.

[kristinapathak]

Discussion with the team today led to these decisions:

1. Caduceus will not do anything to parse or determine the Device ID.
2. We will remove the Matcher field in the webhook struct for the webhook registration API, and remove logic in Caduceus that uses it.
3. Add a new required field in the WRP SimpleEvent that indicates the DeviceID. Caduceus will no longer have a special header for the Device ID specifically and instead will have a header for it that matches the other fields.

Most of these decisions affect other repos. The main change needed for this issue is for Caduceus to no longer use the webhook Matcher field for anything, and to only use the wrphttp package to add the wrp headers.