Add section on required image-builder dependency versions

[abhay-krishna]

Add section to image-builder docs regarding required dependency versions.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from abhay-krishna. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• docs/OWNERS

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

All modified and coverable lines are covered by tests ✅

Project coverage is 72.37%. Comparing base (a77f775) to head (2b8c663).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9000   +/-   ##
=======================================
  Coverage   72.37%   72.37%           
=======================================
  Files         578      578           
  Lines       45451    45451           
=======================================
+ Hits        32894    32897    +3     
+ Misses      10826    10824    -2     
+ Partials     1731     1730    -1     

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

[abhay-krishna]

/cherrypick release-0.21

[eks-distro-pr-bot]

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

In response to this:

/cherrypick release-0.21

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/test-infra repository.

[abhay-krishna]

/cherrypick release-0.20

[eks-distro-pr-bot]

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

In response to this:

/cherrypick release-0.20

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/test-infra repository.

[eks-distro-pr-bot]

@abhay-krishna: new pull request created: #9070

In response to this:

/cherrypick release-0.21

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/test-infra repository.

[eks-distro-pr-bot]

@abhay-krishna: new pull request created: #9071

In response to this:

/cherrypick release-0.20

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/test-infra repository.

[abhay-krishna]

/cherrypick release-0.19

[eks-distro-pr-bot]

@abhay-krishna: #9000 failed to apply on top of branch "release-0.19":

Applying: Add section on required image-builder dependency versions
Using index info to reconstruct a base tree...
M	docs/content/en/docs/osmgmt/artifacts.md
Falling back to patching base and 3-way merge...
Auto-merging docs/content/en/docs/osmgmt/artifacts.md
CONFLICT (content): Merge conflict in docs/content/en/docs/osmgmt/artifacts.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add section on required image-builder dependency versions
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-0.19

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/test-infra repository.