Description of problem:

According to https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html, the 'options' element for the 'route' attribute in a CF manifest is optional.
However, when the 'options' element is not specified for the 'route' attribute in the CF manifest used as input to the discover command, the discover command throws this error.

Error: field validation for key 'Application.Routes.Routes[0].Options.LoadBalancing' field 'LoadBalancing' failed on the 'oneof' tag

Version-Release number of selected component (if applicable):

$ mta-cli version
version: 7.3.0
SHA: eb5652ff7bb90d74c2dc92848d20171db39f206b
image: registry.redhat.io/mta/mta-cli-rhel9:7.3.0

How reproducible:

Always

Steps to Reproduce:

1.$ mta-cli discover cloud-foundry --input cf-nodejs-app-mod.yaml
Error: field validation for key 'Application.Routes.Routes[0].Options.LoadBalancing' field 'LoadBalancing' failed on the 'oneof' tag

Actual results:

When the 'options' element is not specified for the 'route' attribute in CF manifest , the discover command throws an error.

Expected results:

'Options' element under the 'route' attribute should be made optional

Additional info: