Improve the UX around bindings

[dmikusa]

What happened?

It's super common for users to attach a binding at build time to pack build, but then forget or not understand that it's also required to have the binding present at runtime. When run without the binding at runtime, the service will typically not work because it is missing credentials and other critical info.

• What were you attempting to do?

• What did you expect to happen?

What I think would be reasonable is for libpak to log binding information, like it does with configuration information (the ConfigurationResolver.

Obviously, we wouldn't log the actual value, since that is sensitive information, but we could log the bindings that are visible and perhaps the binding keys that are present, that way a user can see they have bindings set up correctly (getting this set up is tricky).

We can also log a message like, "Buidlpacks do not store bindings in generated images. Please remember to also mount your bindings when you actually run your container images.". Perhaps even link to some docs that explains it more.

• What was the actual behavior? Please provide log output, if possible.

Nothing. Bindings will be present and may or may not be used. It's confusing and difficult to debug when there are issues.

Checklist

• I have included log output.
• The log output includes an error message.
• I have included steps for reproduction.