Handle new cloud-init error code and status

Jira: https://issues.redhat.com/browse/RHEL-114958

     - A new error code [1] was introduced in cloud-init v23.4, RedHat team reported
    that our OVT code shall handle this new error code properly, see
    https://github.com/vmware/open-vm-tools/issues/768.
    This change follows the backwards-compatible way in
    https://cloudinit.readthedocs.io/en/latest/explanation/return_codes.html
    to check that the return code is not equal to 1.
    
     - Running status has been changed from "not run" to "not started" in
    cloud-init v24.1, see details in
    https://github.com/canonical/cloud-init/commit/d175170aedc1398b85ac767573b8773a5a2e7c6f.
    This change adds "not started" match to CLOUDINIT_STATUS_NOT_RUN.
    
    This patch was sent by John Wolfe over email and has been pushed upstream here:
    https://github.com/vmware/open-vm-tools/blob/Handle-new-cloud-init-error-code.patch/

    Addresses open-vm-tools issue https://github.com/vmware/open-vm-tools/issues/768
    
    This change has been tested internally by Amy Chen and is seen to fix the
    original issue.
    
    1. https://cloudinit.readthedocs.io/en/latest/explanation/failure_states.html#error-codes
    
    Signed-off-by: Ani Sinha <anisinha@redhat.com>