feat: expose persistent playout state on LSG

[Julusian]

About the Contributor

This pull request is posted on behalf of the BBC

Type of Contribution

This is a: Feature

New Behavior

It would be useful to expose some arbitrary playout state via the LSG without having to insert (and then find it) in random pieces.

We already have this concept of PersistentPlayoutState within the blueprints, which is modifiable in the blueprint playout methods.
This expands that to have a 'public' and 'private' forms of that, similar to how we have publicData and privateData elsewhere.

The public version is then exposed via LSG, with the private one kept as before.

Because we have this BlueprintPlayoutPersistentStore wrapper around the state, to allow us to detect changes without a diff, instead of adding another property to blueprint methods, this has been expanded to wrap both versions of this state.

Testing

• I have added one or more unit tests for this PR
• I have updated the relevant unit tests
• No unit test changes are needed for this PR

Affected areas

Time Frame

Other Information

Status

• PR is ready to be reviewed.
• The functionality has been tested by the author.
• Relevant unit tests has been added / updated.
• Relevant documentation (code comments, system documentation) has been added / updated.

[codecov]

Codecov Report

❌ Patch coverage is 58.04196% with 60 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
meteor/server/migration/X_X_X.ts	35.55%	29 Missing ⚠️
...lueprints/context/services/PersistantStateStore.ts	47.05%	18 Missing ⚠️
...c/playout/model/implementation/PlayoutModelImpl.ts	44.44%	5 Missing ⚠️
packages/job-worker/src/playout/take.ts	42.85%	4 Missing ⚠️
...ckages/job-worker/src/playout/timeline/generate.ts	0.00%	3 Missing ⚠️
...e-status-gateway/src/topics/activePlaylistTopic.ts	50.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!