🌱 Add items to cache immediately after apply

[lentzi90]

What this PR does / why we need it:

Add items to cache immediately after apply to avoid extra no-op patch just for caching.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Part of #12291

[k8s-ci-robot]

[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 assign sbueringer for approval. For more information see the 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:

• OWNERS

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

[lentzi90]

Hmm race detected. I wonder if that could be a genuine issue from the code change 🤔
/test pull-cluster-api-test-main

[sbueringer]

Should be unrelated to your PR . I'll take a closer look during review. Also very likely the race is just in test code (fake client)

[sbueringer]

Suggested change

	// Convert to unstructured WITHOUT filtering to preserve server fields (like resourceVersion)
	objectAfterApplyUnstructured := &unstructured.Unstructured{}
	err = env.GetScheme().Convert(objectAfterApply, objectAfterApplyUnstructured, nil)
	g.Expect(err).ToNot(HaveOccurred())

This is not necessary (anymore), right?
We can just use the resourceVersion from objectAfterApply

[lentzi90]

Yes you are right, fixed

[sbueringer]

@lentzi90 Thank you very much. Last nit. I also tested it with Tilt and it works perfectly

[lentzi90]

Thanks! Fixed the last nit. Do you want me to squash the commits? I kept the changes to ComputeRequestIdentifier on a separate commit for now since I wasn't sure if we wanted it.