Don't shell parse all config values

[ekcasey]

What happened?

We shouldn't shell parse all configuration values. Some values are not shell words and fail to parse, resulting in failed builds. Instead buildpacks that accept shell word configuration should parse these values.

• What were you attempting to do?
  Using the paketo sample jar app: https://github.com/paketo-buildpacks/samples/tree/main/java/jar

  pack build samples/jar --env BP_OCI_DESCRIPTION="some(example)string" --builder paketobuildpacks/builder:base
  

• What did you expect to happen?

  A successful build with label key org.opencontainers.image.description set to value some(example)string

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

  Paketo Image Labels Buildpack 2.0.6
    https://github.com/paketo-buildpacks/image-labels
  
  Paketo Image Labels Buildpack 2.0.6
    unable to create configuration resolver
    unable to parse value
    invalid command line string
  

Build Configuration

• What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
  using? Please include a version.

  pack version
  0.16.0+git-e0f6c50.build-1898
  

• What buildpacks are you using? Please include versions.

  Paketo Image Labels Buildpack 2.0.6
    https://github.com/paketo-buildpacks/image-labels
  

• What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?

  paketobuildpacks/builder:base
  

• Can you provide a sample app or relevant configuration (buildpack.yml,
  nginx.conf, etc.)?

  https://github.com/paketo-buildpacks/samples/tree/main/java/jar

Checklist

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