feat: add support for HyperDeck devices

[from-the-river-to-the-sea]

This PR adds support for the following HyperDeck commands:

• Play
• Record
• Preview

"Stop" is implicit and is defined as the absence of any of the above commands.

The other commands (Forward, Rewind, Jog, and Shuttle) really only make sense for manual control of the device and are unlikely to be supported. Fast forward and rewind functionality can already be achieved via the speed parameter of the Play command.

This branch has been tested extensively and is currently being used in a live production.

This PR will be ready to merge once nrkno/sofie-timeline-state-resolver#213 is merged and a new nightly release is available (if we're okay using a nightly release of TSR, that is).

[from-the-river-to-the-sea]

The linter errors are due to TSR not being updated yet and should go away once we have an appropriate nightly.

[nytamin]

Looks good!

Could you go through the list below, then I'd be happy to merge this:

• Adress the review comment
• Update TSR dependency to 7.3.0-nightly-release44-20220914-085659-53fbc9650.0, which contains the hyperdeck-PR
• Test that it works and builds
• Update README
• Set this PR to "ready to review" and re-request a review from me :)

[from-the-river-to-the-sea]

7.3.0-nightly-release44-20220914-085659-53fbc9650.0 does not appear to contain the HyperDeck PR. This may be because said PR landed on the release46 branch, not release44.

[nytamin]

Ah my mistake, try this one instead: 7.4.0-nightly-release46-20220915-075618-de36c07ee.0

[from-the-river-to-the-sea]

I'm not sure why, but uncaught exceptions are being thrown whenever the sideload connection fails to connect or times out. Below is an example:

[1] 2022-09-15T14:26:17.888Z [electron] info: TELEMETRY: {"reportType":"application-error","error":"Uncaught exception: Error: connect ETIMEDOUT 192.168.0.10:9993","errorStack":"Origin: uncaughtException","date":"2022-9-15","version":"0.9.1","osType":"Windows_NT","osRelease":"10.0.19044","osPlatform":"win32"}
[1] 2022-09-15T14:26:17.888Z [electron] error: Uncaught exception: Error: 
connect ETIMEDOUT 192.168.0.10:9993
[1] Origin: uncaughtException

I'm not sure where the problem lies. Is it an issue with hyperdeck-connection itself?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

[from-the-river-to-the-sea]

I'm not sure why, but uncaught exceptions are being thrown whenever the sideload connection fails to connect or times out.

Whoops, you can ignore this. I had simply forgotten to rebuild the shared packages before testing a change.