Don't always try to set locked status of security accounts

[brinnjoyce]

Closes #598

This would still run into permissions issues if the account was locked or if you tried to manually define the locked status. But it allows a security account like the below to be created on an FSx Ontap

resource "netapp-ontap_security_account" "harvest" {
  cx_profile_name = var.fsx_cx_profile_name
  name            = "harvest"
  applications = [
    {
      application            = "ontapi"
      authentication_methods = ["password"]
    }
  ]
  password = var.harvest_password
  role = {
    name = "fsxadmin-readonly"
  }
}

[chuyich]

Fine with the first change But think about the case I shared in the comment.

[suhasbshekar]

We try to avoid defaults going forward as API may change defaults in future, this creates a dependency, lets try to have a solution without default

[suhasbshekar]

We try to avoid defaults going forward as API may change defaults in future, this creates a dependency, lets try to have a solution without default