Bug: Schemas(management_security. ssl_profiles[x].tls_versions) can be a float type as well

Issue Summary

management_security. ssl_profiles[x].tls_versions can be either str or float. Although the provided input is correct the schema was raising warnings because float type was missed in the supported types.

Also, the description should have info that the values can be float or a string (space separated values)

Which component(s) of AVD impacted

eos_cli_config_gen

How do you run AVD ?

Ansible CLI (with virtual-env or native python)

Steps to reproduce

management_security:
  ssl_profiles:
    - name: test_profile
      tls_versions: 1.2


The above data-model is a valid one, which is similar to the below.

```yaml
management_security:
  ssl_profiles:
    - name: test_profile
      tls_versions: "1.2"

### Relevant log output

_No response_

### Contributing Guide

- [X] I agree to follow this project's Code of Conduct

[ClausHolbechArista]

@gmuloc I will hold back on the pattern, since we need to enhance that feature in the schemas first. But I added examples in #2247 to make it more clear. I also added automatic type-conversion from float to str.

[gmuloc]

Adding to this we could add a pattern for the string in the schema while revisiting this to check that it is a space separated list of “float like” strings