This will break Storybook. Time ago will always be changing! Is something broken rn?

Thisfixes Storybook,not breaks it.

To understand why not have dynamicnew Date()s in our mocks, see that@Emyrk 's PR that touches only the backend here:

#1569

is causing a changeset in chromatic:https://www.chromatic.com/test?appId=624de63c6aacee003aa84340&id=628544a245901b004586ba74

@vapurrmaid I believe this will fix that page, but break the Workspaces page timestamps in Storybook.

@vapurrmaid it's probably best if Storybook page instances decide to use static vs. dynamic time themselves. Because there could be requirements to displayago on one page, and a specific timestamp on another, it seems like it'll be hard to standardize.