Switch from CoInitialize to CoInitializeEx

[RebeccaMahany]

I noticed some errors in the logs for the test devices with the watchdog enabled:

encountered error checking if watchdog task exists: creating schedule service object: CoInitialize has not been called.

We have already called CoInitialize immediately prior to creating the schedule service object, so this error doesn't make a ton of sense.

When looking through the go-ole issues, I found go-ole/go-ole#124 and go-ole/go-ole#246, both of which seem to indicate that calling CoInitialize instead of CoInitializeEx may be the culprit. I've updated accordingly.

My test device has not emitted this error, but I have regression tested that publishing watchdog logs works; I also tested reinstalling the watchdog task.

This is not a terribly high-priority item -- I think the worst this error could do is prevent us from publishing watchdog logs.

[James-Pickett]

LGTM, I'll wait for @zackattack01 to review

[zackattack01]

this makes sense to me, thank you!