Don't warn about clear-env key while parsing buildpack.toml as this is actually expected.

[fumblehool]

Fixes #2253

Summary

Output

Before

24: Pulling from heroku/builder
Digest: sha256:28390a2f5e326a0e32f041e934c0d509757d2aab0c33bb9476569557e29b8c99
Status: Image is up to date for heroku/builder:24
24: Pulling from heroku/heroku
Digest: sha256:2363090f27c848b67a06a3a269dac13f042ffeed61af27432bd3bad360ed1d0e
Status: Image is up to date for heroku/heroku:24
Warning: Ignoring unexpected key(s) in descriptor for buildpack testing-buildpack: buildpack.clear-env
Warning: Builder is trusted but additional modules were added; using the untrusted (5 phases) build flow
===> ANALYZING
[analyzer] Image with name "test-image" not found
===> DETECTING
[detector] ========

After

24: Pulling from heroku/builder
Digest: sha256:28390a2f5e326a0e32f041e934c0d509757d2aab0c33bb9476569557e29b8c99
Status: Image is up to date for heroku/builder:24
24: Pulling from heroku/heroku
Digest: sha256:2363090f27c848b67a06a3a269dac13f042ffeed61af27432bd3bad360ed1d0e
Status: Image is up to date for heroku/heroku:24
Warning: Builder is trusted but additional modules were added; using the untrusted (5 phases) build flow
===> ANALYZING
[analyzer] Image with name "test-image" not found
===> DETECTING
[detector] ======== 

Documentation

• Should this change be documented?
  • Yes, see #___
  • No

Related

Resolves #2253

[jjbustamante]

LGTM

We've been having issues with these warnings, can we check if the pkg/dist/buildmodule.go has all the elements from the spec?

[fumblehool]

Hi @jjbustamante
I checked for other keys but only sbom-formats and metadataare not included, as per this comment:

pack/pkg/buildpack/buildpack.go

Line 133 in 86b4bf3

// FIXME: we should ideally update dist.ModuleInfo to expect sbom-formats, but this breaks other tests;

I think, we can try to fix that in separate PR.