Optimization e2e test approach

[tpiperatgod]

Description
The current e2e workflow has the following flaws:

• It is mainly based on the v1beta1 api version instead of the latest v1beta2 api version.
• It takes up too much Action resources.
• Unable to connect components such as builder, functions-framework, and so on.

Therefore, I propose to optimize the e2e workflow:

• Update the test cases to use the v1beta2 api version.
• Provide a mechanism to run locally, and a mechanism to recognize the results of local runs, i.e. when the results of local runs are recognized, then e2e workflow on Action can be skipped.
• Provide e2e workflows through multiple components (e.g., fetch component code from a given branch, build the artifacts separately, and then validate them in a unified way).

[benjaminhuo]

That's great enhancements!

[benjaminhuo]

@B1F030 It'll be great if you can help with this. New PRs still have e2e test failure https://github.com/OpenFunction/OpenFunction/actions/runs/6098005280/job/16546872305?pr=483