Run an Altinn Studio app on a non Altinn provided Kubernetes cluster

### Description

While the goal of Altinn Studio applications is to be independent of the underlying Kubernetes platform provider, we know we have some dependencies on Azure resources like key vault. Some dependencies we know about, others we might not be aware of. This issue aims to verify the known dependencies and identify any unknown issues.

The goal is to provide a verified list of issues that needs to be adressed in order to run on anything as long as it has Kubernetes.

### In scope

This issue applies to Altinn Studio applications only

### Out of scope

Other parts of the Altinn platform is not part of this analysis, meaning shared services will still run in Azure on a platform provided by Digdir.

### Additional Information
Any temporary changes that needs to be done to get progress should be done in TT02 and related to the TTD organization and reverted once the analysis is completed.

### Analysis

_No response_

### Conclusion

_No response_

Start by running an Altinn Studio application in a non-Altinn Kubernetes cluster and reviewing its known Azure resource dependencies. Record both confirmed and newly discovered blockers, make any temporary TT02 changes for the TTD organization, and verify that they are reverted; done means a verified list of requirements for running on Kubernetes outside the Altinn-provided platform.

Written by the indexing model from the issue text.