Issue 6: Changed some of the Hashicorp Vault references in the docs to OpenBao

[naphelps]

References: #6

Changes:

• Issue 6: Changed some of the Hashicorp Vault references in the docs to OpenBao.

[naphelps]

@jessebot Some doc changes. Cleaned up 1 or 2 items that got missed in your pull request.

[JanMa]

The linter CI check currently fails because the Chart needs a version bump whenever files in the charts/openbao folder are changed. Please bump the chart version in the chart.yaml file

[jessebot]

So, we kinda have an issue where even after you bump the chart version, the chart linter will still fail, because there's a few things left over from hashicorp that need to be fixed to please the linter in values.yaml:

• there are some commented lines that don't have a space after the #
• the prometheusRules parameters are indented too far compared to the rest of the values.yaml (how did this ever work? 🤔 )
• the main image is still wrong.

I've addressed all of the above in #8 so you can still do one of the following:

1. force merge this, then I can pull the changes to my fork's main branch, then rebase and force push to my feature branch, and then the tests should pass in my Issue 3: update base vault images to point at quay.io/openbao/openbao; add more helm docs #8 and we can merge that into main for this repo

2. open a PR from with these changes, naphelps:issue-6, to my feature branch in Issue 3: update base vault images to point at quay.io/openbao/openbao; add more helm docs #8, I merge them into my feature branch, and then we merge Issue 3: update base vault images to point at quay.io/openbao/openbao; add more helm docs #8 in

3. I can open a PR to naphelps:issue-6, you can merge my feature branch into naphelps:issue-6, and then we merge this PR into main. Can't do this, GitHub doesn't let me open a PR to that fork for some reason 🤷