rotate the encryption key only when updating an existing cluster that has secret encryption enabled

[release/v1.3] Add pre release notes with k8s versions included

RKE will panic if we enable rotate_encryption_key but disable secrets_encryption_config when creating a cluster. The panic happens because RKE tries to use the rkeConfig, which does not exist. The rkeConfig will be made after the rke up command succeeds.
Solution:
Skip the rotateEncryptionKey operation when creating a new cluster. Also, In this case, keys are just made for the first time, so there is no need to rotate them.

This reverts commit f1ba3150.

update codegen release branch

update kdm data

update branch to release-v2.6

update kdm

[release/v1.3] go generate

delete hostname-override for aws cloud provider

[release/v1.3] Add GitHub Actions workflow for go-generate

aws cloud provider assigns private dns as the node name,
don't override it since it cannot be changed.

Retry query job status when addon is removing during apply

[release/v1.3] Add job complete check in integration