[Feature] Controller for Attestation on Confidential AKS Worker Nodes

**Is your feature request related to a problem? Please describe.**

Not a problem, per se, but a feature that would tie into existing Confidential Computing capabilities. Some AKS-native capability to attest that your code will execute in a confidential enclave, while allowing for (configurable) action to be taken that nodes that fail the attestation, such as drain/cordoning the nodes or labeling them accordingly to avoid having some workloads execute on them.

**Describe the solution you'd like**

When I create an AKS cluster/nodepool with Confidential VMs, I want the ability to optionally configure a feature that would automatically attest my worker nodes, and should they fail the attestation in any way, trigger actions such as draining/cordoning those nodes.

Something like:

```
az aks create
-g \
--name \
--node-vm-size \
--enable-attestation
--action-mode
```

**Describe alternatives you've considered**

I could use one of the other Azure resources, such as the [attestation generation application](https://github.com/Azure/confidential-computing-cvm-guest-attestation/blob/main/aks-linux-sample/cvm-attestation.yaml) to generate the attestation report and action on my node pools myself.

**Additional context**

Main goal of this proposal is a potentially straightforward/automatic way someone would be able to attest their CVM node pools and action on it afterwards. This is submitted to gauge interest, please interact with this feature if you'd be interested 😄 .