Vault-encrypted variables fail string validation

[acidroper]

Description
If the one_pass or context.PASSWORD variables are encrypted with ansible-vault, they fail the validation check:

FAILED! => {
    "assertion": "one_pass is undefined or one_pass is none or one_pass is string",
    "changed": false,
    "evaluated_to": false,
    "msg": "Please make sure [context.PASSWORD, one_pass, one_token, one_version] are valid strings."
}

To Reproduce
Encrypt the one_pass variable with ansible-vault:

one_pass: !vault |
          $ANSIBLE_VAULT;1.1;AES256
          3436396339323131396166663537386532636135316338333134666161613739
          613436373964380a323462306537656364623733396163623765306663343532
          3863366664346632656532363866373734326535653463303563366338363141

Expected behavior
Vault-encrypted variables should pass the validation.

Details

• Ansible version: 2.16.12

Additional context
This issue appears related to ansible/ansible#75646 and could be resolved by implementing the vault_encrypted test.

Progress Status

• Code committed
• Testing - QA
• Documentation (Release notes - resolved issues, compatibility, known issues)