Update ekb to tagged version

[dsimansk]

Description

Changes

• Update ekb to tagged version

I'll need to figure out issue with our auto-update tooling and some kn plugins.

[dsimansk]

/cherry-pick release-1.17

[knative-prow-robot]

@dsimansk: once the present PR merges, I will cherry-pick it on top of release-1.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dsimansk]

/cc @skonto

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.98%. Comparing base (18d2618) to head (41cc4a7).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #369   +/-   ##
=======================================
  Coverage   44.98%   44.98%           
=======================================
  Files          11       11           
  Lines         558      558           
=======================================
  Hits          251      251           
  Misses        292      292           
  Partials       15       15           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[skonto]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, skonto

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 [dsimansk,skonto]

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

[knative-prow-robot]

@dsimansk: new pull request created: #370

In response to this:

/cherry-pick release-1.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.