fix: use user-defined dist folder for last-built-actions.json

[hparra]

Description

Fix hardcoded "dist" folder for 'last-built-actions.json'.

Related Issue

I suspect there are a few more of these, e.g. SSL certs, log forwarding SHA, etc.

Motivation and Context

app.manifest.yaml allows for custom dist folder but not all part of tool respect it.

How Has This Been Tested?

• unit tests
• hot patch + blackbox test: DEBUG=@adobe/aio-lib-runtime* npm run build

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (9bff007) to head (e95d749).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #183   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           11        11           
  Lines         1303      1303           
  Branches       346       346           
=========================================
  Hits          1303      1303           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hparra]

Highly suspect. "Works" but the last-built-actions.json is now nowhere to be seen, even though DEBUG statements and additional hotpatched logs show that it is successfully read.