Support and ownership of apps runtime

### Description

This is an analysis issue regarding support of our users and our ownership of the apps runtime, and how we can improve these aspects from an operational/team perspective. There are a couple of pain points that are all at least a little related

* Development process is slow at times when features require work across systems (e.g. apps & Storage). This also affects the quality of our work in other systems such as Storage, as we are not very familiar with standards, processes, etc
* We are not proactive when it comes to bugs and other operational issues, which means there are latent and common bugs that cause friction between us and our users and other teams on the platform
* We have no insight or access to instance data for debugging purposes, and often have to rely on service owners or team Core to provide additional information
* Our team, due to us working in the center of a lot of things (the runtime tying a lot of things together), usually ends up being involved in a lot of different activities that span the entire platform. This effect is also seen in support, where a lot of the time we end up just being routers for support tickets

These pain points may seem loosely related, and perhaps this issue should be broken up, but I think they all factor into how we perform as a team and how well we serve our users and other teams on the platform

### In scope

TBD

### Out of scope

TBD

### Additional Information

TBD

### Analysis

TBD

### Conclusion

TBD

No files, tests, or code entry points are named. Start by clarifying the scope, ownership questions, and operational pain points described in the issue, then document the agreed in-scope work, out-of-scope items, analysis, and conclusion. Done should be a decided and actionable plan rather than unresolved TBD sections.

Written by the indexing model from the issue text.