Update helm chart to pull chart binary data and values from specified file

[tylerauerbeck]

Is your feature request related to a problem? Please describe.
When writing values files charts for even non-complex deployments, the values file can become quite cluttered due to the values being provided for the deployed chart and the binarydata of the chart that a user wishes to have the operator deploy.

Describe the solution you'd like
We can more cleanly provide these values to the chart by having users provide these values in additional files (i.e. files/chartData and files/chartValues). A user could specify in values.yaml any valid path that our helm chart has access to in values.yaml and then they would be able to provide those values (which are likely to change less often than ones we would be working with in values.yaml). This also would provide us with some separation of values between what we use to deploy the operator (values.yaml) and the chart that we're having the operator deploy (files/chartData and files/chartValues)

Describe alternatives you've considered

• Init containers to pull in the appropriate chart at runtime
  • This doesn't solve the whole problem and actually potentially causes problems for deployments that would want to run without giving the operator access to pull from the internet. This actually has several drawbacks (security of pulling artifacts in from the internet, issues running in airgapped networks, etc.). Even after this, we still don't solve for nested values files.