Move analysis panics into Derived*

[frankmcsherry]

Our analysis framework allows you to build on various other analyses, but to access them you need to probe the collection to get the results, and .. potentially they might not exist (due to a logic bug). There is nothing to do other than panic, and all the "user" code immediately panics with the same messages: "Analysis FOO was required, but is missing".

This PR moves those panics into the analysis container, indicating that some methods may panic when invoked with arguments that cannot be found, not unlike array out of bounds access or key not found errors.

Motivation

Tips for reviewer

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[ggevay]

I like this change. (I think there was even a discussion on the original Analysis framework PR to do this refactoring at some point.)

[frankmcsherry]

There may well have been a discussion, and I should have called out that I didn't invent this idea, I stole it from someone!