data store: dont update outputs incrementally

[oliver-sanders]

An awkward bodge to work around https://github.com/cylc/cylc-flow/issues/6307

I'm not sure we want to go ahead with this, at least not in the long term, however, it should be enough to unblock (at lest the review of) https://github.com/cylc/cylc-ui/pull/1886

Check List

• [ ] I have read CONTRIBUTING.md and added my name as a Code Contributor.
• [ ] Contains logically grouped changes (else tidy your branch by rebase).
• [ ] Does not contain off-topic changes (use other PRs for other changes).
• [ ] Applied any dependency changes to both setup.cfg (and conda-environment.yml if present).
• [ ] Tests are included (or explain why tests are not needed).
• [ ] Changelog entry included if this is a change that can affect users
• [ ] Cylc-Doc pull request opened if required at cylc/cylc-doc/pull/XXXX.
• [ ] If this is a bug fix, PR should be raised against the relevant ?.?.x branch.

[MetRonnie]

Looks like b2accfb885b4a8ea7dce1ad2bfdff4d089ac31b1 (examples: using data to define your workflow) included accidentally?

[oliver-sanders]

(removed)

[oliver-sanders]

Short of a universal solution to #6307, this patch seems a reasonable way to get the info view in the UI off of the ground.