fix(web): add option to override outputPath for file-server

[barbados-clemens]

Current Behavior

when trying to use file-server with an executor that does not have an outputPath property (i.e. storybook) you are unable to serve the artifacts with file-server

Expected Behavior

be able to manually override the outputPath to allow other executors to use file server

Related Issue(s)

Fixes #

[nx-cloud-staging]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c6a1efc. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 12 targets

• nx affected --target=e2e --base=d103cd9d51063f6ab1e06aa25a9de8241f197a0f --head=c6a1efcff0901d08130c34a385efc61675f23428 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox,e2e-make-angular-cli-faster --parallel=1
• nx affected --target=build --base=d103cd9d51063f6ab1e06aa25a9de8241f197a0f --head=c6a1efcff0901d08130c34a385efc61675f23428 --parallel=3
• nx affected --target=test --base=d103cd9d51063f6ab1e06aa25a9de8241f197a0f --head=c6a1efcff0901d08130c34a385efc61675f23428 --parallel=1
• nx-cloud record -- yarn depcheck
• nx affected --target=lint --base=d103cd9d51063f6ab1e06aa25a9de8241f197a0f --head=c6a1efcff0901d08130c34a385efc61675f23428 --parallel=3
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn check-lock-files
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=d103cd9d51063f6ab1e06aa25a9de8241f197a0f --head=c6a1efcff0901d08130c34a385efc61675f23428
• nx-cloud record -- yarn check-imports
• nx-cloud record -- yarn documentation
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Nov 2, 2022 at 4:28PM (UTC)

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.