feat: func run support all build options

[lkingland]

• 🎁 func run supports build options and host (non-containerized) build option

Refactors the run command to include all options from build, in the same manner as deploy.
Updates help text to match the other command format, and lays the verbal groundwork for the difference between containerized (currently default) and non-containerized runs.
Adds the --container flag (currently defaults to true) which will, when disabled, invoke the localhost-based runner which, in this commit, is not yet active.

/kind enhancement

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lkingland

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lkingland]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

Patch coverage: 80.23% and project coverage change: +0.39 🎉

Comparison is base (d5b4a8d) 62.84% compared to head (c082add) 63.23%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1693      +/-   ##
==========================================
+ Coverage   62.84%   63.23%   +0.39%     
==========================================
  Files          93       93              
  Lines       12005    12049      +44     
==========================================
+ Hits         7544     7619      +75     
+ Misses       3772     3745      -27     
+ Partials      689      685       -4     

Flag	Coverage Δ
e2e-test	39.20% <73.65%> (+0.31%)	⬆️
e2e-test-oncluster	34.72% <46.10%> (+0.08%)	⬆️
e2e-test-oncluster-runtime	29.68% <46.10%> (?)
e2e-test-runtime-go	28.36% <46.10%> (?)
e2e-test-runtime-node	29.51% <46.10%> (?)
e2e-test-runtime-python	29.51% <46.10%> (?)
e2e-test-runtime-quarkus	29.65% <46.10%> (?)
e2e-test-runtime-springboot	28.54% <46.10%> (?)
e2e-test-runtime-typescript	29.65% <46.10%> (?)
integration-tests	50.25% <78.44%> (+0.25%)	⬆️
unit-tests-macos-latest	49.04% <78.44%> (+0.19%)	⬆️
unit-tests-ubuntu-latest	49.97% <78.44%> (+0.24%)	⬆️
unit-tests-windows-latest	49.12% <78.44%> (+0.22%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
cmd/client.go	88.75% <ø> (-0.14%)	⬇️
cmd/root.go	79.47% <ø> (+1.83%)	⬆️
pkg/functions/client.go	65.03% <0.00%> (+0.41%)	⬆️
pkg/functions/function.go	77.92% <ø> (ø)
pkg/functions/job.go	65.21% <0.00%> (-4.56%)	⬇️
cmd/run.go	77.93% <82.69%> (+6.86%)	⬆️
cmd/deploy.go	75.75% <83.33%> (-0.06%)	⬇️

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[lance]

Looks great! I just have a couple of nits - and it needs a rebase.

[lance]

I wonder if this should somehow be communicated to the user.

[lkingland]

Yes and at least one time when I was using run locally, specifying --builder, I was confused why it didn't use the same value the next time around.

So on the one hand I am pretty sure that we do not want invocations of run to persist the value of flags which alter deploy (and build), but I also find that once accustomed to the value of flags persisting between commands, I expect them to be consistently persistent.

The only solution that comes to mind is that we actually have a separate set of flag values for running (a development/testing, inner-loop sort of paradigm) vs those used for the deployed function. These would be developer-specific (host scoped) and reside in .func/ in the same way as --remote, etc.

This more complete solution is probably complex enough to warrant its own issue and PR, so for the purposes of this PR I just want to make sure that invoking run with a different builder during development/testing doesn't alter the deployed function configuration!

[lance]

/lgtm