Develop access to computed Values as present within Helm

Summary

We found issues in !134 (merged) caused by the order of "stacking" the Values passed to Template. CR's spec.values are superseded Operator's internal defaults. We found that we don't actually have all of the stacked values, as one would get from helm get values -a in COMPUTED VALUES: output.

Details

During the development / testing of !131 (merged), !133 (merged), and subsequent !134 (merged), we found that the expectations that Values was parity to that within Helm itself was not correct. While we can continue development without this, having the ability to treat as such would be very helpful. We should look into a method of making such accessible, if possible. Being able to access in this way, post rendering, would gain us access to these, and allow for a bit finer control of the whole & resolved Values.