feat: untimed parts

[jstarpl]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

This is a new feature.

• What is the current behavior? (You can also link to an open issue here)

All playable parts are counted towards show time and as-played time - unless they are "invalid" or "floated", which renders them unplayable.

• What is the new behavior (if this is a feature change)?

A Part can be marked as "untimed" which will keep them playable, but cause them to:

• not trigger blueprints "firstTake" callback

• not set startedPlayback on a playlist when they are taken, the startedPlayback will be set once a not-"untimed" part is taken

• not count towards segment time budget

• there will be a countdown to the end of an "untimed" part (unless it's expectedDuration is 0) and the "On Air In" counter will also be affected by the duration of an "untimed" part.

• Other information:

Status

• Code documentation for the relevant parts in the code have been added/updated by the PR author
• The functionality has been tested by the PR author
• The functionality has been tested by NRK

[codecov-commenter]

Codecov Report

Merging #512 (8c815ea) into release34 (0e68b3c) will decrease coverage by 0.87%.
The diff coverage is 100.00%.

❗ Current head 8c815ea differs from pull request most recent head 7dc4cf0. Consider uploading reports for the commit 7dc4cf0 to get more accurate results

@@              Coverage Diff              @@
##           release34     #512      +/-   ##
=============================================
- Coverage      66.48%   65.60%   -0.88%     
=============================================
  Files            250      240      -10     
  Lines          15064    14239     -825     
  Branches        3515     3328     -187     
=============================================
- Hits           10015     9342     -673     
+ Misses          4883     4733     -150     
+ Partials         166      164       -2     

Impacted Files	Coverage Δ
meteor/lib/collections/Parts.ts	52.77% <ø> (ø)
meteor/server/api/blueprints/events.ts	76.25% <100.00%> (+0.30%)	⬆️
meteor/server/api/playout/take.ts	60.24% <100.00%> (ø)
packages/server-core-integration/src/index.ts
.../server-core-integration/src/lib/configManifest.ts
...server-core-integration/src/lib/corePeripherals.ts
...kages/server-core-integration/src/lib/ddpClient.ts
...ckages/server-core-integration/src/lib/watchDog.ts
packages/server-core-integration/src/lib/random.ts
packages/server-core-integration/src/lib/queue.ts
... and 3 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e68b3c...7dc4cf0. Read the comment docs.

[Julusian]

It looks like the events used for metadatabank will still be called (onRundownTimingEvent), but that could be appropriate as things did happen and the blueprints can easily filter out the parts that are untimed if it desired, so I am happy with this

Other than that it looks all good to me