Graph API supports bi-directional updates for Releases (Playnite Games)

[andrew-codes]

Playnite Web Releases can have certain properties updated via the Graph API that will reflect in both Playnite and Playnite Web.

Note that relational properties must be handled individually for every entity type in Playnite. Currently this PR enables the Graph API to support Playnite Games' features. Soon to be included completion status, too. Others will be considered additional features and will have a dedicated issue for each.
Note this does not enable a UI to support updating data. This will be handled in a future PR.

The following cases are handled:

• Sending an update to the Graph API for non-relational properties and Playnite is running, then the update is applied to Playnite.
• Updates applied to Playnite via the Graph API for non-relational properties, will synchronizec back to Playnite Web automatically when successfully updating Playnite.
• One or more updates are sent to the Graph API, while Playnite is not running. Each update is applied in chronological order once Playnite comes back online.
• Graph API provides a subscription for entity updates. When an entity is updated from Playnite, subscribers are notified of the change. This allows automatically updating the UI with fresh data.
• Playnite game features relational property is supported for updates (add and remove)
• duplicated adds and removes are ignored
• adds or removes with invalid Oids are ignored

Closes #569
Closes #696
Relates to #461
Closes #668

BREAKING CHANGE - MQTT update messages have changed. The message topic taxonomy, payload shape, and persistence have changed. Update and connection messages are not persistent. Bi-directional updates rely on persistent message in MQTT. Please see the setup documentation for an example Mosquitto configuration file to enable persistence. Please see MQTT documentation for changes to message formats.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.12%. Comparing base (8cf3c07) to head (25c0042).
Report is 47 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (8cf3c07) and HEAD (25c0042). Click for more details.

HEAD has 3 uploads less than BASE

Flag	BASE (8cf3c07)	HEAD (25c0042)
unit-tests	2	1
component-tests	2	1
e2e-tests	2	1

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #711      +/-   ##
==========================================
- Coverage   61.00%   51.12%   -9.89%     
==========================================
  Files          98      103       +5     
  Lines        2003     2173     +170     
  Branches      442      482      +40     
==========================================
- Hits         1222     1111     -111     
- Misses        773      993     +220     
- Partials        8       69      +61     

Flag	Coverage Δ
component-tests	36.04% <ø> (ø)
e2e-tests	60.23% <ø> (-13.29%)	⬇️
unit-tests	8.40% <ø> (-0.91%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

🎉 This PR is included in version 11.0.0 🎉

The release is available on:

• v11.0.0
• GitHub release

Your semantic-release bot 📦🚀