Add a set of performance benchmark

[Shell32-Natsu]

There are some reports about the kustomize performance reduction, like #2987, #2869. And we also have PRs try to improve the performance, like #3172. These issues and PRs should be based on a performance benchmark so that we can accurately estimate and assess the performance reduction or improvement.

This set of benchmark should:

• Has enough workloads to show the difference of performance between different versions
• Has good coverage and use as more kustomize features as possible.

One option is converting the examples into a set of benchmark. However, the size of it may be not enough so we may need to repeat it multiple times.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[Shell32-Natsu]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[shapirus]

See also #5422 for ideas and/or a possible implementation of certain pieces.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted