Cleanup test and example bundles

[carolynvs]

What does this change

• We have finished vetting using ghcr.io with Porter and it has been more
  stable than Docker Hub. So we are going to stop publishing our images
  and example bundles to Docker Hub and only publish to ghcr.io
  I will leave the old assets up at Docker Hub and they will continue to
  be available for the forseeable future.

• Bump the version on the example bundles. We should have done this as
  soon as we cut a 1.0.0 release of Porter, since it ended up publishing
  examples over the top of existing ones that were compatible with v0.38

  Well it's too late to fix that, but we can make sure we bump the version
  number when we move to ghcr.io. Later we can optionally go back and
  republish the bundles from stable if needed (which will always host with
  docker hub, we aren't moving the old stable example bundles to ghcr.io)

• Add an optional parameter to the hello bundle, along with an output for
  the name passed in, so that we can continue to use it as a test bundle
  for the operator. Testing with a bundle that doesn't have inputs/outputs
  managed to miss a number of key problems with the operator so this will
  be helpful.

• Our test bundles shouldn't reference a real registry, it increases the
  change that we may accidentally push them to a live registry. Setting
  registry to localhost:5000 ensures that when we build/publish test
  bundles that they stay on your local machine.

What issue does it fix

Closes #1280

Notes for the reviewer

I recommend looking through this by commit instead of all at once. I've grouped related changes which should make it easier to get through this big PR.

Checklist

• Did you write tests?
• Did you write documentation?
• Did you change porter.yaml or a storage document record? Update the corresponding schema file.
• If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Reviewer Checklist

• Comment with /azp run test-porter-release if a magefile or build script was modified
• Comment with /azp run porter-integration if it's a non-trivial PR

[carolynvs]

/azp run test-porter-release

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[carolynvs]

/azp run test-porter-release

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).