SPIKE - Define values yaml that reflects the future state of bb-common.

Currently bb-common supports a small subset of planned resource generation, namely focusing on NetworkPolicies. However the plan for bb-common includes tackling numerous other components of a Big Big packages.

The roadmap includes:

* **Authorization Policies**: Istio authorization templates
* **Service Entries**: External service registration
* **Peer Authentications**: mTLS configuration
* **Virtual Services**: Traffic management rules

It would be helpful to spend some time casting more vision into the future for what values bb-common collects in an effort more collectively plan for what is coming in terms of both package integration as well as how it affects the deployment within Big Bang umbrella.

This goal of this spike would entail defining a values.yaml example that represents the desired end state of information collected from bb-commom.

For example a values.yaml that might include something like:

networkPolicies: ...

istio: ...

routes: ...

sso: ...

monitoring: ...

policyExceptions: ...