fix: update-kind-example-to-containerd_1.5

[dmitrynovik]

What this PR does / why we need it:

Adjusted the example of running the kapp-controller in kind for the containerd 1.5+

The example supplied in this repository, kapp-controller in kind, no longer works with my containerd://1.7.1 - the pods are scheduled and created, but there are image pull errors as every pod tries to pull image over HTTPS instead of HTTP ( as in this StackOverflow example).

I believe this change happened in containerd v1.5 as each container needs a hosts.toml file.
This new requirement is also reflected in project kind: create a local registry, note a new step which is missing in the 2 year old kind-with-registry.sh script:

# 3. Add the registry config to the nodes
#
# This is necessary because localhost resolves to loopback addresses that are
# network-namespace local.
# In other words: localhost in the container is not localhost on the host.
#
# We want a consistent name that works from both ends, so we tell containerd to
# alias localhost:${reg_port} to the registry container when pulling images
REGISTRY_DIR="/etc/containerd/certs.d/localhost:${reg_port}"
for node in $(kind get nodes); do
  docker exec "${node}" mkdir -p "${REGISTRY_DIR}"
  cat <<EOF | docker exec -i "${node}" cp /dev/stdin "${REGISTRY_DIR}/hosts.toml"
[host."http://${reg_name}:5000"]
EOF
done

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?

NONE
-->

Additional Notes for your reviewer:

Review Checklist:

• Follows the developer guidelines
• Relevant tests are added or updated
• Relevant docs in this repo added or updated
• Relevant carvel.dev docs added or updated in a separate PR and there's
  a link to that PR
• Code is at least as readable and maintainable as it was before this
  change

Additional documentation e.g., Proposal, usage docs, etc.:

[praveenrewar]

Thank you for making the contribution. Could you please sign your commits to make the DCO bot happy, we can merge the PR then.

[praveenrewar]

@dmitrynovik I think the rebase didn't work so there are some commits coming up from develop. Could you please take a look at it?
(You might have to do a reset before rebase and then rebase again)