Bump function-runner to v7.0.1

[adampetro]

WHY are these changes introduced?

Bump to latest version of function-runner

WHAT is this pull request doing?

Bump the version that is downloaded

How to test your changes?

• rm -r packages/app/dist/cli/services/bin/ (clear out any cached downloaded binaries)
• pnpm shopify app function build --path <path_to_function_extension> (downloads and runs Javy)
• cat <path_to_function_input> | pnpm shopify app function run --path <path_to_function_extension> (downloads and runs function-runner)

Post-release steps

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes - not applicable

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.25% (+0.02% 🔼)	8873/11792
🟡	Branches	70.45% (+0.03% 🔼)	4327/6142
🟡	Functions	75.03%	2323/3096
🟡	Lines	75.8% (+0.02% 🔼)	8388/11066

Test suite run success

2000 tests passing in 904 suites.

Report generated by 🧪jest coverage report action from f16483e

[isaacroldan]

Question, if the binary is already there, it won't download the new version right?
Do we have a mechanism to force updates?

[adampetro]

Question, if the binary is already there, it won't download the new version right?

Correct

Do we have a mechanism to force updates?

Yes, the user bumping the version of the CLI NPM package. The binary is downloaded to a path within the package, so when the package is bumped to a newer version, it's a new directory so the binary shouldn't be there.