Flake: Tinkerbell `TestReconcilerReconcileControlPlaneFailure`

```
--- FAIL: TestReconcilerReconcileControlPlaneFailure (0.10s)
client.go:91: Try updating status but failed with a 404 error for [distro.eks.amazonaws.com/v1alpha1, Kind=Release name=test namespace=eksa-system] object, most probably because it doesn't have a defined status subresource
reconciler_test.go:284:
Unexpected error:
<*errors.withStack | 0xc0012ea768>: {
error: <*errors.withMessage | 0xc000fa9c40>{
cause: <*errors.StatusError | 0xc0012503c0>{
ErrStatus: {
TypeMeta: {Kind: "", APIVersion: ""},
ListMeta: {
SelfLink: "",
Failed to retrieve log lines: couldn't read requested bytes: error reading from artifact: EOF
},
stack: [0x156b3e5, 0x156f656, 0x1a5093e, 0x1a4bb89, 0x52baeb, 0x470241],
}
building Config from a cluster client: TinkerbellMachineConfig.anywhere.eks.amazonaws.com "cp-machine-config" not found
occurred
FAIL
coverage: 88.7% of statements
Stopping the test environment
FAIL github.com/aws/eks-anywhere/pkg/providers/tinkerbell/reconciler 16.846s
```

https://prow.eks.amazonaws.com/view/s3/prowpresubmitsdataclusterstack-prowbucket7c73355c-vfwwxd2eb4gp/pr-logs/pull/aws_eks-anywhere/5152/eks-anywhere-presubmit/1632785315179532288

Start by running TestReconcilerReconcileControlPlaneFailure in the Tinkerbell reconciler package and review the failure at reconciler_test.go:284. Then inspect the status update at client.go:91 and the reported missing TinkerbellMachineConfig; done means the test passes reliably without the 404 or missing-config error.

Written by the indexing model from the issue text.