Add process specific working directories

[imnitishng]

Summary

• Show process' working directory from the WorkingDirectory param in metadata label
• If working directory from label is empty then use Image's inspect to figure out the working directory (stored as WorkingDir)
  This PR depends on Add WorkingDir() to return image working directory imgutil#141, I did not find a way to expose the working directory so I had to go for this change, let me know if there's another way to handle the problem.
  Moreover, I had to update a bunch of dependencies to actually get the newly added WorkingDirectory param inside of process, which means go.mod and go.sum are modified.
  I think we'll need to update the PR again with the new imgutil release if we decide to merge both PRs and go this route, if not then I'd be happy to work on the feedback.
  Tests will be failing until we merge the PR for imgutil

Output

Before

After

Documentation

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

Related

#1422

Resolves #1422

[imnitishng]

Updating the PR soon, with passing test 😬

[imnitishng]

I think we should be good to go once buildpacks/imgutil#144 is merged

[imnitishng]

Hey @jromero, I am having issues with the spacing for WORK DIR, for windows and linux.
The spacing for both the platforms is a bit different, but the template is same.
Should I create new template files .txt for windows and linux? Or should we modify the test in some other way?
Once this is fixed, we should be good to go.

[jromero]

Hey @jromero, I am having issues with the spacing for WORK DIR, for windows and linux. The spacing for both the platforms is a bit different, but the template is same. Should I create new template files .txt for windows and linux? Or should we modify the test in some other way? Once this is fixed, we should be good to go.

I can see the issue in Windows. It looks as though because WORK DIR comes after ARGS and on windows, args are pushing the column further to the right.

Based on our conversation on #buildpacks-platform. I'd be comfortable removing the acceptance test for human-readable output comparison.

In otherwords, deleting these lines (L976-L980, L1627-L1631) and any associated resources from pack_fixtures.