Create assetdata

[justinsb]

We create some yaml files that record the hashes for well-known file assets,
and then we will be able to look them up by their canonical URL.

This is not yet actually used, that can be done in a future commit.

[hakman]

Very nice. Should make things much faster.
Could we remove all arch that we don't need from k8s and runc data and merge them into a single file instead of one per version?
Also, generate-*.sh files may be easier to use from hack/.

[justinsb]

Good suggestions - agree with all of them!

• I moved the script to hack/generate-asset-hashes.sh.
• I exclude some of the most obvious things we don't need for k8s, to try to reduce the asset size. We could also go the other way I guess, and build them up with e.g. --include (i.e. just kubelet / kubectl I think).
• I combined them into one file per major, rather than one file per patch (i.e. k8s-1.28.yaml vs k8s-1.28.1.yaml). This feels like a reasonable trade-off, because then we will just see whole files drop off as we stop supporting those k8s versions (though it's not time critical that we do so)

[hakman]

I guess the only thing left is to pass shellcheck.

In ./hack/generate-asset-hashes.sh line 18:
cd "${REPO_ROOT}"
^---------------^ SC2164 (warning): Use 'cd ... || exit' or 'cd ... || return' in case cd fails.

Did you mean: 
cd "${REPO_ROOT}" || exit

For more information:
  https://www.shellcheck.net/wiki/SC2164 -- Use 'cd ... || exit' or 'cd ... |...

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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 [hakman]

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