fix: fix streambundle error after port to TypeScript

[bkeepers]

This fixes an error reported by @KEGustafsson introduced in #1918. I have not been able to recreate it, but apparently there are instances where update.values is present, but is not an array. Looking back at #1918, it looks like the old code did have an if conditional, so there must be instances where it is null/undefined. I updated the types to be consistent with the implementation as well.

While I was looking at that, I noticed that app is injected into stream bundle, but is unused, so I removed it in another commit.

[tkurki]

I can’t think of a use case for values not being an array, so i would rather implement a check-and-discard in handleMessage so that downstream one can expect valid data. @panaaj @sbender9 @KEGustafsson ?

[sbender9]

Just don't forget about meta deltas, where "values" may be undefined.

[KEGustafsson]

This and #1942 seemed to fix recently seen problems.
I could try to spend couple of minutes to check what actually caused issues.

[KEGustafsson]

It is meta causing this issue . Added try-catch to collect deltas and here is small piece of the log throwing error.

Apr 16 17:23:34 { "meta": [ { "path": "notifications.mob", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.205Z" }
Apr 16 17:23:34 { "meta": [ { "path": "notifications.fire", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.209Z" }
Apr 16 17:23:34 { "meta": [ { "path": "notifications.sinking", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.212Z" }
Apr 16 17:23:34 { "meta": [ { "path": "notifications.flooding", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.214Z" }
Apr 16 17:23:34 { "meta": [ { "path": "notifications.collision", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.216Z" }
Apr 16 17:23:34 { "meta": [ { "path": "notifications.grounding", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.218Z" }
Apr 16 17:23:34 { "meta": [ { "path": "notifications.listing", "value": { "supportsPut": true } } ], "$source": "freeboard-sk", "timestamp": "2025-04-16T17:23:34.219Z" }

[bkeepers]

I can’t think of a use case for values not being an array, so i would rather implement a check-and-discard in handleMessage so that downstream one can expect valid data.

Sounds good, I updated handleMessage. I tried adding some tests for this behavior, but adding unit tests was going to require some refactoring that belongs in a pull request of its own.

[bkeepers]

Prettier's 80 char line limit is so annoying. Most of these changes are because line 282 is now just over 80 characters, and now it's hard to see what else I actually changed. Anyone opposed to changing it to 100 characters?

Here's a link to view the diff without whitespace changes