bug(al2023): Do not bind containerd restarts to kubelet

[cartermckinnon]

Issue #, if available:

Fixes #1846.

Description of changes:

This updates the kubelet.service on AL2023 to be loosely-coupled with containerd, so that restarts/kills of containerd do not impact kubelet.

We're not making this change on AL2 because folks may see different behavior if they're starting/stopping either of these units in their existing user data.

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

[cartermckinnon]

/ci

[github-actions]

@cartermckinnon roger that! I've dispatched a workflow. 👍

[github-actions]

@cartermckinnon the workflow that you requested has completed. 🎉

AMI variant	Build	Test
1.21 / al2	success ✅	success ✅
1.22 / al2	success ✅	success ✅
1.23 / al2	success ✅	success ✅
1.23 / al2023	success ✅	success ✅
1.24 / al2	success ✅	success ✅
1.24 / al2023	success ✅	success ✅
1.25 / al2	success ✅	success ✅
1.25 / al2023	success ✅	success ✅
1.26 / al2	success ✅	success ✅
1.26 / al2023	success ✅	success ✅
1.27 / al2	success ✅	success ✅
1.27 / al2023	success ✅	success ✅
1.28 / al2	success ✅	failure ❌
1.28 / al2023	success ✅	success ✅
1.29 / al2	success ✅	success ✅
1.29 / al2023	success ✅	success ✅
1.30 / al2	success ✅	success ✅
1.30 / al2023	success ✅	success ✅

[cartermckinnon]

The 1.28 / al2 failure was a network flake, not related.