Establish perf goals for application startup and runtime execution in containerized environments

[This item was copied from the planning repo]

Through 7.0, we'll continue to augment the container segment of our benchmarks and improve the reporting in an effort to gain clear insight into guidance we can give customers on how to best run .NET apps and microservices in constrained (virtual/containerized) environments to address frequently asked questions such as:

- What's the lowest-size container I can use before my app starts to malfunction?
- How many containerized .NET apps can/should I run on one machine?
- What's the best practice for scaling *down* once an app successfully scales *up* to support a burst or load?

We'll address these (and a series of other) questions as we observe the benchmarks. Once we get close to 7.0, we'll author a paper with clear guidance for customers on how best to run .NET in containers at scale, based on a variety of scenarios (and probably a fair number of caveats).

- We'd like 10 customers who would be willing to review (or contribute to) the paper and who would be willing to apply the learnings and guidance we summarize in a real project, then report back their findings from our paper and guidance.
- Revisit the customer success upon application of the guidance.

By 8, have *very* clear guidance and maybe, configuration guidance or tool pre-configurations that make it easy for cloud-native developers to get going with the greatest density - or greatest saturation - possible based on their needs and our findings.