Update lifecycle from v0.16.1 to v0.17.0

[edmorley]

Of note, this adds support for Platform API 0.12 and Buildpack API 0.10 (ready for when the Heroku CNB build system and CNBs support them):
https://github.com/buildpacks/spec/releases/tag/platform%2Fv0.12
https://github.com/buildpacks/spec/releases/tag/buildpack%2Fv0.10

Release notes:
https://github.com/buildpacks/lifecycle/releases/tag/v0.16.2
https://github.com/buildpacks/lifecycle/releases/tag/v0.16.3
https://github.com/buildpacks/lifecycle/releases/tag/v0.16.4
https://github.com/buildpacks/lifecycle/releases/tag/v0.16.5
https://github.com/buildpacks/lifecycle/releases/tag/v0.17.0

Commits:
buildpacks/lifecycle@v0.16.1...v0.17.0

GUS-W-13977966.

[edmorley]

Hmm the new lifecycle output is quite verbose, eg:

===> ANALYZING
Timer: Analyzer started at 2023-08-19T15:09:42Z
Image with name "getting-started" not found
Timer: Analyzer ran for 33.202µs and ended at 2023-08-19T15:09:42Z
===> DETECTING
Timer: Detector started at 2023-08-19T15:09:42Z
heroku/python   0.5.0
heroku/procfile 2.0.0
Timer: Detector ran for 6.10975ms and ended at 2023-08-19T15:09:42Z
===> RESTORING

(https://github.com/heroku/builder/actions/runs/5912102145/job/16035204379?pr=377#step:6:7)

I'll report a few suggestions upstream next week.

[edmorley]

I've filed GUS-W-13981419 to track reporting this upstream.

In the meantime we can still merge this, since the verbosity increase is tolerable, and it would be good to pick up the other changes in 0.17.0.