Automation Update

[lkingland]

Our primary repository's automation is flaky, has several actions with overlapping functionality, and local make targets have diverged from those run in CI. In general we should probably:

• Remove Functions-specific actions which are now covered by the Knative common tooling.
• Update the Makefile targets to run the internals of these tests as closely as possible locally (i.e. make test should be effectively equialent to the GitHub Action, ideally running the same script if possible. This would, for example run linters with the same options locally as in CI).
• Transition to using the shared Knatve quick-start for allocating the cluster, in hopes it is less flaky (cluster allocation often fails with timeouts due to apparently having allocated resources of a potato).
• Update the build/test flags to be test with or without integration tests, rather than the current configuration of disjunct sets.
• Review our E2E tests to identify areas of possible optimization
• Investigate if we can disable the Prow bot's auto-assign of reviewers

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.