Add basic values translation script, example 1.x defaults

General MR

Summary

Provides a basic values translation script for the main key changes for package names. The approach taken is:

• basic checks to validate the values file provided exists, gnu-sed is present
• sed replacement of core packages, replacing the first match where the line starts with the old name.
• sed replacement of addon packages, replacing the first match where the line starts with any number of spaces + the old name.

Other approaches considered:

• yq usage: yq does not have a great way to change a key. Effectively you need to create a new key (set equal to the old one) then delete the new one. This has weird effects on order in the file, and combined with the way yq strips out extra lines it makes for a messy script that doesn't really work.
• Some hybrid yq/sed approach: Initially I wanted more "smarts" around editing the specific key, rather than just a regex match of what I think is the key. yq provides a way to get the line number for a key which seemed promising, but because of the way yq strips blank lines this proved to not be effective either.
• Something else entirely: I considered looking at other available tools/options but given that this was meant to be a simple script that helps in some situations I decided to just settle with the sed approach.

Also adds an example 1.x default core package values file.

blog/2-0-breaking-changes.md

 ---
-revision_date: Last edited April 13, 2023
+revision_date: Last edited April 14, 2023
 tags:
   - blog
 ---
@@ -19,7 +19,7 @@ As mentioned in the first post, a number of values keys will be changing in orde
 - `mattermostoperator` -> `mattermostOperator`
 - `nexus` -> `nexusRepositoryManager`
 
-Note that your upgrade to 2.0 will fail if you do not modify your values as seen above. Big Bang is now maintaining a [values schema](https://helm.sh/docs/topics/charts/#schema-files) to enforce strict adherence to the allowed/required keys within Big Bang. For reference Big Bang's values schema is located [here](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/values.schema.json).
+Note that your upgrade to 2.0 will fail if you do not modify your values as seen above. Big Bang is now maintaining a [values schema](https://helm.sh/docs/topics/charts/#schema-files) to enforce strict adherence to the allowed/required keys within Big Bang. For reference Big Bang's values schema is located [here](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/values.schema.json). You can also leverage the script in `/scripts/values-translate-2-0.sh <values file path>` to perform these translations for you (note that this is a relatively simple script and may not work for your use case).
 
 ## Namespace Changes
 
@@ -49,7 +49,7 @@ As mentioned in the previous post - Big Bang will deploy by default with a new o
 - Gatekeeper: Set `gatekeeper.enabled` and `clusterAuditor.enabled` to true; set `kyverno.enabled`, `kyvernoReporter.enabled`, and `kyvernoPolicies.enabled` to false
 - Jaeger: Set `jaeger.enabled` to true; set `tempo.enabled` to false
 
-Provided you make the above adjustments you will be able to deploy with the same set of packages you were using in 1.x.
+Provided you make the above adjustments you will be able to deploy with the same set of packages you were using in 1.x. Example values for each of the above are provided in a reference file [here](../docs/assets/configs/example/core-packages-1-x.yaml).
 
 ## HelmRelease / GitRepository Name Changes