Split chart and app code

After a long discussion on Mattermost, we've decided that we would like to split the chart/ directory off from the application code so that we can develop bbctl without considering the chart as directly, and handle the chart like any other bbctl package, with an ironbank -> renovate process. This will reduce the complexity of the release code as well as reduce the number of MRs in the bbctl repository. It also allows us to consider the two bbctl projects separately and reduce tight coupling and dependencies.

Risks

• The Ironbank pipeline is expecting to see the images published at a specific point and will be needed to be updated
• Any other references to the binary locations (e.g. homebrew, docs) will need to be updated

Acceptance Criteria

• bbctl as it stands is moved to a new location
• bbctl is forked into the existing location (https://repo1.dso.mil/big-bang/product/packages/bbctl) where packages are expected
• MRs are created in both to remove the chart from the app code and the app code from the chart
• All references are updated (homebrew, docs, ironbank) to point at the correct respecting places
• Release code is updated to remove the chart/app code distinctions

References

• homebrew-tools-public reference to the current bbctl repo: https://repo1.dso.mil/big-bang/homebrew-tools-public/-/blob/main/Formula/bbctl.rb?ref_type=heads#L7
• bbctl's brew formula generator also has a reference that will need updating: https://repo1.dso.mil/big-bang/product/packages/bbctl/-/blob/main/scripts/brewer/templates/bbctl.rb.tmpl?ref_type=heads#L7