Fixes bug for options that do not have a type

What does this MR do and why?

Fixes input options where no type is specified. For example, in the following config:

spec:
  inputs:
    VARIABLE_NAME:
      default: 0
      options:
        - 0
        - 1
      description: The variable in question.
---

before:

This will error unless type: number is specified, as it will assume the value provided is a string and when it does validate_options it checks for the inclusion of a string "1" in an array like: [0, 1] :

after:

References

#536914 (closed)

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.