feat(nimbus): setup results page with required data

[moibra05]

Because

• Results page view context requires specific data to render contents

This commit

• Passes the required context data through the view

Fixes #13682

[mikewilli]

I left some suggestions inline, but overall it's looking pretty close.

One thing to be aware of is that the schemas/ folder actually contains its own python package that is published separately from Experimenter. This means you'll want to update and publish a new version in a separate PR if you want to make changes to it (you can see the schemas/README file for docs on this). However, see my comments inline there for a potential alternative approach.

[mikewilli]

Let me know if you want to discuss my concerns, maybe I'm misinterpreting what will happen here or maybe we just need to figure out a better way to approach this.

It also might be appropriate to split this out into two PRs that separates the client changes from the UI changes.

[mikewilli]

Ok I left too many comments, this is largely good as-is. My main concern is with the has_exposures logic, everything else is relatively small suggestions.

[mikewilli]

LGTM thanks!

[mikewilli]

If you wanted to be more concise, you could keep the static parts in the function and only put the dynamic stuff (the parts that go in weekly and overall) in here. This is OK for now though.