fix: force build on every aio app run (for switching from remote and local contexts)

[shazron]

Description

Fixes #542
(see issue for use case)

In a nutshell, we will always force deploy actions on every aio app run (doesn't matter if there are no code changes).

How Has This Been Tested?

npm test
manual test

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

Merging #551 (17266b8) into master (6c7ca51) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #551   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           50        50           
  Lines         2600      2600           
  Branches       472       473    +1     
=========================================
  Hits          2600      2600           

Impacted Files	Coverage Δ
src/lib/build-actions.js	100.00% <100.00%> (ø)
src/lib/run-dev.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c7ca51...17266b8. Read the comment docs.

[shazron]

need to test for a new use case:

1. aio app run --local
2. use curl to connect to the local action, get success/error.
3. run aio app run --local again
4. use curl to connect to the local action again, Expected: success/error (not resource not found/404)

Action code is never saved on the local server, you will always have to redeploy code.

[shazron]

new use case: passes (I was in a wrong branch before)

[moritzraho]

lgtm!

[purplecabbage]

this seems like it should have been handled by the pr that added build caching
I doubt it would have been written any differently though ...
looks good to me!